From bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Fri Jan 13 11:13:28 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 11:13:28 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Fri Jan 13 11:13:28 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 11:13:28 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Fri Jan 13 11:13:28 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Fri Jan 13 11:13:28 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Fri Jan 13 11:13:28 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 11:13:28 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Fri Jan 13 11:13:28 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Fri Jan 13 11:13:28 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 11:13:28 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Fri Jan 13 11:13:28 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Jan 13 11:13:28 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Fri Jan 13 11:13:28 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Jan 13 11:13:28 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 11:13:28 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Jan 13 11:13:28 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 11:13:28 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Jan 13 11:13:28 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 11:13:28 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Jan 13 11:13:28 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Fri Jan 13 11:13:28 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Fri Jan 13 11:13:28 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Jan 13 11:13:28 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Fri Jan 13 15:13:59 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0001.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 15:13:59 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Fri Jan 13 15:14:00 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 15:14:00 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Fri Jan 13 15:14:00 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Fri Jan 13 15:14:00 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0001.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Fri Jan 13 15:14:00 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 15:14:00 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Fri Jan 13 15:14:00 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Fri Jan 13 15:14:00 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 15:14:00 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Fri Jan 13 15:14:00 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Jan 13 15:14:00 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Fri Jan 13 15:14:00 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Jan 13 15:14:00 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0001.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 15:14:00 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Jan 13 15:14:00 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 15:14:00 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Jan 13 15:14:00 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 15:14:00 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Jan 13 15:14:00 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Fri Jan 13 15:14:00 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Fri Jan 13 15:14:00 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Jan 13 15:14:00 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Fri Jan 13 15:21:25 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0002.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 15:21:25 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Fri Jan 13 15:21:25 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 15:21:25 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Fri Jan 13 15:21:25 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Fri Jan 13 15:21:25 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0002.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Fri Jan 13 15:21:25 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 15:21:25 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Fri Jan 13 15:21:25 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Fri Jan 13 15:21:25 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 15:21:25 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Fri Jan 13 15:21:25 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Jan 13 15:21:25 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Fri Jan 13 15:21:25 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Jan 13 15:21:25 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0002.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 15:21:25 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Jan 13 15:21:25 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 15:21:25 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Jan 13 15:21:25 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 15:21:25 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Jan 13 15:21:25 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Fri Jan 13 15:21:25 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Fri Jan 13 15:21:25 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Jan 13 15:21:25 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Fri Jan 13 16:00:55 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0003.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 16:00:55 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Fri Jan 13 16:00:55 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 16:00:55 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Fri Jan 13 16:00:55 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Fri Jan 13 16:00:55 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0003.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Fri Jan 13 16:00:55 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 16:00:55 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Fri Jan 13 16:00:55 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Fri Jan 13 16:00:55 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 16:00:55 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Fri Jan 13 16:00:56 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Jan 13 16:00:56 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Fri Jan 13 16:00:56 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Jan 13 16:00:56 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0003.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 16:00:56 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Jan 13 16:00:56 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 16:00:56 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Jan 13 16:00:56 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 16:00:56 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Jan 13 16:00:56 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Fri Jan 13 16:00:56 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Fri Jan 13 16:00:56 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Jan 13 16:00:56 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Fri Jan 13 20:01:54 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0004.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 20:01:55 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Fri Jan 13 20:01:55 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 20:01:55 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Fri Jan 13 20:01:55 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Fri Jan 13 20:01:55 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0004.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Fri Jan 13 20:01:55 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 20:01:55 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Fri Jan 13 20:01:55 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Fri Jan 13 20:01:55 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 20:01:55 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Fri Jan 13 20:01:55 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Jan 13 20:01:55 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Fri Jan 13 20:01:55 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Jan 13 20:01:55 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0004.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 20:01:55 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Jan 13 20:01:55 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 20:01:55 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Jan 13 20:01:55 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 20:01:55 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Jan 13 20:01:55 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Fri Jan 13 20:01:56 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Fri Jan 13 20:01:56 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Jan 13 20:01:56 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Sat Jan 14 08:02:30 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0005.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 08:02:31 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Sat Jan 14 08:02:31 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 08:02:31 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Sat Jan 14 08:02:31 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Sat Jan 14 08:02:31 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0005.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Sat Jan 14 08:02:31 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 08:02:31 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Sat Jan 14 08:02:31 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Sat Jan 14 08:02:31 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 08:02:31 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Sat Jan 14 08:02:31 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Jan 14 08:02:31 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sat Jan 14 08:02:31 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Jan 14 08:02:31 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0005.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 08:02:31 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Jan 14 08:02:31 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 08:02:31 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Jan 14 08:02:31 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 08:02:31 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Jan 14 08:02:31 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Sat Jan 14 08:02:31 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sat Jan 14 08:02:31 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Jan 14 08:02:31 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Sat Jan 14 12:00:54 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0006.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 12:00:54 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Sat Jan 14 12:00:54 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 12:00:54 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Sat Jan 14 12:00:54 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Sat Jan 14 12:00:54 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0006.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Sat Jan 14 12:00:54 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 12:00:54 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Sat Jan 14 12:00:54 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Sat Jan 14 12:00:54 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 12:00:54 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Sat Jan 14 12:00:54 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Jan 14 12:00:54 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sat Jan 14 12:00:54 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Jan 14 12:00:55 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0006.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 12:00:55 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Jan 14 12:00:55 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 12:00:55 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Jan 14 12:00:55 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 12:00:55 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Jan 14 12:00:55 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Sat Jan 14 12:00:55 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sat Jan 14 12:00:55 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Jan 14 12:00:55 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Sat Jan 14 16:00:51 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0007.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 16:00:51 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Sat Jan 14 16:00:51 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 16:00:51 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Sat Jan 14 16:00:51 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Sat Jan 14 16:00:51 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0007.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Sat Jan 14 16:00:51 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 16:00:51 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Sat Jan 14 16:00:51 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Sat Jan 14 16:00:51 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 16:00:51 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Sat Jan 14 16:00:51 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Jan 14 16:00:51 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sat Jan 14 16:00:51 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Jan 14 16:00:51 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0007.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 16:00:51 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Jan 14 16:00:51 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 16:00:51 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Jan 14 16:00:52 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 16:00:52 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Jan 14 16:00:52 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Sat Jan 14 16:00:52 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sat Jan 14 16:00:52 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Jan 14 16:00:52 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Sat Jan 14 20:00:50 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0008.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 20:00:52 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Sat Jan 14 20:00:52 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 20:00:52 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Sat Jan 14 20:00:52 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Sat Jan 14 20:00:52 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0008.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Sat Jan 14 20:00:52 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 20:00:52 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Sat Jan 14 20:00:52 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Sat Jan 14 20:00:52 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 20:00:52 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Sat Jan 14 20:00:52 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Jan 14 20:00:52 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sat Jan 14 20:00:52 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Jan 14 20:00:52 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0008.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 20:00:52 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Jan 14 20:00:52 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 20:00:52 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Jan 14 20:00:52 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 20:00:52 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Jan 14 20:00:52 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Sat Jan 14 20:00:52 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sat Jan 14 20:00:52 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Jan 14 20:00:52 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Sun Jan 15 08:02:19 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0009.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 08:02:19 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Sun Jan 15 08:02:19 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 08:02:19 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Sun Jan 15 08:02:19 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Sun Jan 15 08:02:19 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0009.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Sun Jan 15 08:02:19 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 08:02:19 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Sun Jan 15 08:02:19 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Sun Jan 15 08:02:19 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 08:02:19 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Sun Jan 15 08:02:19 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Jan 15 08:02:19 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sun Jan 15 08:02:19 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Jan 15 08:02:19 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0009.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 08:02:19 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Jan 15 08:02:19 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 08:02:19 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Jan 15 08:02:19 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 08:02:19 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Jan 15 08:02:19 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Sun Jan 15 08:02:19 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sun Jan 15 08:02:19 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Jan 15 08:02:19 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Sun Jan 15 12:00:59 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0010.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 12:00:59 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Sun Jan 15 12:00:59 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 12:00:59 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Sun Jan 15 12:00:59 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Sun Jan 15 12:00:59 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0010.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Sun Jan 15 12:00:59 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 12:00:59 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Sun Jan 15 12:00:59 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Sun Jan 15 12:00:59 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 12:00:59 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Sun Jan 15 12:00:59 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Jan 15 12:00:59 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sun Jan 15 12:00:59 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Jan 15 12:00:59 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0010.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 12:00:59 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Jan 15 12:00:59 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 12:00:59 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Jan 15 12:00:59 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 12:00:59 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Jan 15 12:00:59 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Sun Jan 15 12:00:59 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sun Jan 15 12:00:59 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Jan 15 12:00:59 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Sun Jan 15 16:00:51 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0011.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 16:00:51 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Sun Jan 15 16:00:51 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 16:00:51 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Sun Jan 15 16:00:51 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Sun Jan 15 16:00:52 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0011.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Sun Jan 15 16:00:52 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 16:00:52 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Sun Jan 15 16:00:52 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Sun Jan 15 16:00:52 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 16:00:52 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Sun Jan 15 16:00:52 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Jan 15 16:00:52 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sun Jan 15 16:00:52 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Jan 15 16:00:52 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0011.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 16:00:52 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Jan 15 16:00:52 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 16:00:52 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Jan 15 16:00:52 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 16:00:52 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Jan 15 16:00:52 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Sun Jan 15 16:00:52 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sun Jan 15 16:00:52 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Jan 15 16:00:52 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Sun Jan 15 20:00:50 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0012.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 20:00:50 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Sun Jan 15 20:00:50 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 20:00:51 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Sun Jan 15 20:00:51 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Sun Jan 15 20:00:51 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0012.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Sun Jan 15 20:00:51 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 20:00:51 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Sun Jan 15 20:00:51 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Sun Jan 15 20:00:51 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 20:00:51 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Sun Jan 15 20:00:51 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Jan 15 20:00:51 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sun Jan 15 20:00:51 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Jan 15 20:00:51 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0012.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 20:00:51 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Jan 15 20:00:51 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 20:00:51 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Jan 15 20:00:51 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 20:00:51 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Jan 15 20:00:51 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Sun Jan 15 20:00:51 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sun Jan 15 20:00:51 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Jan 15 20:00:51 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Mon Jan 16 08:02:41 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0013.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 08:02:41 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Mon Jan 16 08:02:41 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 08:02:41 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Mon Jan 16 08:02:41 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Mon Jan 16 08:02:41 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0013.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Mon Jan 16 08:02:41 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 08:02:42 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Mon Jan 16 08:02:42 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Mon Jan 16 08:02:42 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 08:02:42 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Mon Jan 16 08:02:42 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Jan 16 08:02:42 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Mon Jan 16 08:02:42 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Jan 16 08:02:42 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0013.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 08:02:42 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Jan 16 08:02:42 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 08:02:42 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Jan 16 08:02:42 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 08:02:42 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Jan 16 08:02:42 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Mon Jan 16 08:02:42 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Mon Jan 16 08:02:42 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Jan 16 08:02:42 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Mon Jan 16 12:00:55 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0014.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 12:00:55 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Mon Jan 16 12:00:55 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 12:00:55 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Mon Jan 16 12:00:55 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Mon Jan 16 12:00:55 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0014.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Mon Jan 16 12:00:55 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 12:00:55 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Mon Jan 16 12:00:55 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Mon Jan 16 12:00:55 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 12:00:55 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Mon Jan 16 12:00:55 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Jan 16 12:00:55 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Mon Jan 16 12:00:55 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Jan 16 12:00:55 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0014.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 12:00:55 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Jan 16 12:00:55 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 12:00:55 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Jan 16 12:00:55 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 12:00:55 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Jan 16 12:00:55 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Mon Jan 16 12:00:55 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Mon Jan 16 12:00:55 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Jan 16 12:00:55 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Mon Jan 16 16:00:55 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0015.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 16:00:55 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Mon Jan 16 16:00:55 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 16:00:55 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Mon Jan 16 16:00:55 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Mon Jan 16 16:00:55 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0015.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Mon Jan 16 16:00:55 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 16:00:55 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Mon Jan 16 16:00:55 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Mon Jan 16 16:00:55 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 16:00:55 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Mon Jan 16 16:00:55 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Jan 16 16:00:55 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Mon Jan 16 16:00:55 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Jan 16 16:00:55 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0015.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 16:00:55 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Jan 16 16:00:55 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 16:00:55 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Jan 16 16:00:55 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 16:00:55 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Jan 16 16:00:55 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Mon Jan 16 16:00:55 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Mon Jan 16 16:00:55 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Jan 16 16:00:55 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Mon Jan 16 20:00:52 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0016.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 20:00:52 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Mon Jan 16 20:00:52 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 20:00:52 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Mon Jan 16 20:00:52 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Mon Jan 16 20:00:52 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0016.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Mon Jan 16 20:00:52 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 20:00:52 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Mon Jan 16 20:00:52 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Mon Jan 16 20:00:52 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 20:00:52 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Mon Jan 16 20:00:53 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Jan 16 20:00:53 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Mon Jan 16 20:00:53 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Jan 16 20:00:53 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0016.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 20:00:53 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Jan 16 20:00:53 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 20:00:53 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Jan 16 20:00:53 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 20:00:53 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Jan 16 20:00:53 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Mon Jan 16 20:00:53 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Mon Jan 16 20:00:53 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Jan 16 20:00:53 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Tue Jan 17 08:02:44 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0017.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 08:02:44 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Tue Jan 17 08:02:44 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 08:02:44 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Tue Jan 17 08:02:44 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Tue Jan 17 08:02:44 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0017.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Tue Jan 17 08:02:44 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 08:02:44 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Tue Jan 17 08:02:44 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Tue Jan 17 08:02:44 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 08:02:44 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Tue Jan 17 08:02:44 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Jan 17 08:02:44 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Tue Jan 17 08:02:45 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Jan 17 08:02:45 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0017.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 08:02:45 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Jan 17 08:02:45 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 08:02:45 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Jan 17 08:02:45 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 08:02:45 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Jan 17 08:02:45 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Tue Jan 17 08:02:45 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Tue Jan 17 08:02:45 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Jan 17 08:02:45 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Tue Jan 17 12:01:13 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0018.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 12:01:13 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Tue Jan 17 12:01:13 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 12:01:13 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Tue Jan 17 12:01:13 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Tue Jan 17 12:01:13 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0018.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Tue Jan 17 12:01:13 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 12:01:13 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Tue Jan 17 12:01:13 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Tue Jan 17 12:01:13 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 12:01:13 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Tue Jan 17 12:01:13 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Jan 17 12:01:13 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Tue Jan 17 12:01:13 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Jan 17 12:01:13 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0018.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 12:01:13 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Jan 17 12:01:13 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 12:01:13 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Jan 17 12:01:13 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 12:01:13 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Jan 17 12:01:13 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Tue Jan 17 12:01:13 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Tue Jan 17 12:01:13 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Jan 17 12:01:13 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Tue Jan 17 16:00:59 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0019.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 16:00:59 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Tue Jan 17 16:00:59 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 16:00:59 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Tue Jan 17 16:00:59 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Tue Jan 17 16:00:59 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0019.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Tue Jan 17 16:00:59 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 16:00:59 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Tue Jan 17 16:00:59 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Tue Jan 17 16:00:59 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 16:00:59 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Tue Jan 17 16:00:59 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Jan 17 16:00:59 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Tue Jan 17 16:00:59 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Jan 17 16:00:59 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0019.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 16:00:59 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Jan 17 16:00:59 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 16:00:59 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Jan 17 16:00:59 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 16:00:59 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Jan 17 16:00:59 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Tue Jan 17 16:00:59 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Tue Jan 17 16:00:59 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Jan 17 16:00:59 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Tue Jan 17 20:00:58 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0020.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 20:00:58 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Tue Jan 17 20:00:58 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 20:00:58 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Tue Jan 17 20:00:58 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Tue Jan 17 20:00:58 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0020.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Tue Jan 17 20:00:58 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 20:00:58 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Tue Jan 17 20:00:58 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Tue Jan 17 20:00:58 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 20:00:58 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Tue Jan 17 20:00:59 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Jan 17 20:00:59 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Tue Jan 17 20:00:59 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Jan 17 20:00:59 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0020.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 20:00:59 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Jan 17 20:00:59 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 20:00:59 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Jan 17 20:00:59 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 20:00:59 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Jan 17 20:00:59 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Tue Jan 17 20:00:59 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Tue Jan 17 20:00:59 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Jan 17 20:00:59 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Wed Jan 18 08:04:31 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0021.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 08:04:31 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Wed Jan 18 08:04:31 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 08:04:31 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Wed Jan 18 08:04:31 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Wed Jan 18 08:04:31 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0021.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Wed Jan 18 08:04:31 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 08:04:31 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Wed Jan 18 08:04:31 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Wed Jan 18 08:04:31 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 08:04:31 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Wed Jan 18 08:04:31 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Jan 18 08:04:31 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Wed Jan 18 08:04:31 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Jan 18 08:04:32 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0021.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 08:04:32 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Jan 18 08:04:32 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 08:04:32 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Jan 18 08:04:32 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 08:04:32 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Jan 18 08:04:32 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Wed Jan 18 08:04:32 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Wed Jan 18 08:04:32 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Jan 18 08:04:32 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Wed Jan 18 12:01:13 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0022.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 12:01:13 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Wed Jan 18 12:01:13 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 12:01:13 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Wed Jan 18 12:01:13 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Wed Jan 18 12:01:13 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0022.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Wed Jan 18 12:01:13 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 12:01:13 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Wed Jan 18 12:01:13 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Wed Jan 18 12:01:13 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 12:01:13 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Wed Jan 18 12:01:13 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Jan 18 12:01:13 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Wed Jan 18 12:01:13 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Jan 18 12:01:13 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0022.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 12:01:13 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Jan 18 12:01:13 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 12:01:13 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Jan 18 12:01:13 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 12:01:13 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Jan 18 12:01:13 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Wed Jan 18 12:01:13 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Wed Jan 18 12:01:13 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Jan 18 12:01:13 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Wed Jan 18 16:01:44 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0023.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 16:01:44 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Wed Jan 18 16:01:44 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 16:01:44 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Wed Jan 18 16:01:44 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Wed Jan 18 16:01:44 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0023.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Wed Jan 18 16:01:44 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 16:01:44 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Wed Jan 18 16:01:45 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Wed Jan 18 16:01:45 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 16:01:45 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Wed Jan 18 16:01:45 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Jan 18 16:01:45 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Wed Jan 18 16:01:45 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Jan 18 16:01:45 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0023.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 16:01:45 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Jan 18 16:01:45 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 16:01:45 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Jan 18 16:01:45 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 16:01:45 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Jan 18 16:01:45 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Wed Jan 18 16:01:45 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Wed Jan 18 16:01:45 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Jan 18 16:01:45 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Wed Jan 18 20:01:04 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0024.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 20:01:04 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Wed Jan 18 20:01:04 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 20:01:04 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Wed Jan 18 20:01:05 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Wed Jan 18 20:01:05 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0024.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Wed Jan 18 20:01:05 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 20:01:05 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Wed Jan 18 20:01:05 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Wed Jan 18 20:01:05 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 20:01:05 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Wed Jan 18 20:01:05 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Jan 18 20:01:05 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Wed Jan 18 20:01:05 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Jan 18 20:01:05 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0024.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 20:01:05 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Jan 18 20:01:05 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 20:01:05 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Jan 18 20:01:05 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 20:01:05 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Jan 18 20:01:05 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Wed Jan 18 20:01:05 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Wed Jan 18 20:01:05 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Jan 18 20:01:05 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Thu Jan 19 08:04:52 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0025.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 08:04:52 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Thu Jan 19 08:04:53 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 08:04:53 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Thu Jan 19 08:04:53 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Thu Jan 19 08:04:53 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0025.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Thu Jan 19 08:04:53 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 08:04:53 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Thu Jan 19 08:04:53 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Thu Jan 19 08:04:53 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 08:04:53 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Thu Jan 19 08:04:53 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Thu Jan 19 08:04:53 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Thu Jan 19 08:04:53 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Thu Jan 19 08:04:53 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0025.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 08:04:53 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Thu Jan 19 08:04:53 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 08:04:53 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Thu Jan 19 08:04:53 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 08:04:53 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Thu Jan 19 08:04:53 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Thu Jan 19 08:04:53 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Thu Jan 19 08:04:53 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Thu Jan 19 08:04:53 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Thu Jan 19 12:01:11 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0026.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 12:01:11 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Thu Jan 19 12:01:11 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 12:01:11 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Thu Jan 19 12:01:11 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Thu Jan 19 12:01:11 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0026.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Thu Jan 19 12:01:11 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 12:01:11 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Thu Jan 19 12:01:11 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Thu Jan 19 12:01:11 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 12:01:11 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Thu Jan 19 12:01:11 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Thu Jan 19 12:01:11 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Thu Jan 19 12:01:11 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Thu Jan 19 12:01:11 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0026.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 12:01:11 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Thu Jan 19 12:01:11 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 12:01:11 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Thu Jan 19 12:01:11 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 12:01:11 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Thu Jan 19 12:01:11 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Thu Jan 19 12:01:11 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Thu Jan 19 12:01:11 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Thu Jan 19 12:01:11 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Thu Jan 19 16:03:32 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0027.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 16:03:32 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Thu Jan 19 16:03:33 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 16:03:33 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Thu Jan 19 16:03:33 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Thu Jan 19 16:03:33 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0027.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Thu Jan 19 16:03:33 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 16:03:33 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Thu Jan 19 16:03:33 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Thu Jan 19 16:03:33 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 16:03:33 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Thu Jan 19 16:03:33 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Thu Jan 19 16:03:34 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Thu Jan 19 16:03:34 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Thu Jan 19 16:03:34 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0027.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 16:03:34 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Thu Jan 19 16:03:34 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 16:03:34 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Thu Jan 19 16:03:34 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 16:03:34 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Thu Jan 19 16:03:35 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Thu Jan 19 16:03:35 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Thu Jan 19 16:03:35 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Thu Jan 19 16:03:35 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Thu Jan 19 20:00:56 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0028.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 20:00:56 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Thu Jan 19 20:00:56 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 20:00:56 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Thu Jan 19 20:00:56 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Thu Jan 19 20:00:56 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0028.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Thu Jan 19 20:00:56 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 20:00:56 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Thu Jan 19 20:00:56 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Thu Jan 19 20:00:56 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 20:00:56 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Thu Jan 19 20:00:56 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Thu Jan 19 20:00:56 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Thu Jan 19 20:00:56 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Thu Jan 19 20:00:56 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0028.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 20:00:56 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Thu Jan 19 20:00:56 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 20:00:56 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Thu Jan 19 20:00:56 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 20:00:56 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Thu Jan 19 20:00:56 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Thu Jan 19 20:00:56 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Thu Jan 19 20:00:56 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Thu Jan 19 20:00:56 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Fri Jan 20 08:07:52 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0029.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 08:07:52 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Fri Jan 20 08:07:52 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 08:07:52 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Fri Jan 20 08:07:52 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Fri Jan 20 08:07:53 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0029.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Fri Jan 20 08:07:53 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 08:07:53 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Fri Jan 20 08:07:53 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Fri Jan 20 08:07:53 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 08:07:53 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Fri Jan 20 08:07:53 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Jan 20 08:07:53 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Fri Jan 20 08:07:53 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Jan 20 08:07:53 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0029.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 08:07:53 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Jan 20 08:07:53 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 08:07:53 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Jan 20 08:07:53 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 08:07:53 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Jan 20 08:07:53 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Fri Jan 20 08:07:53 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Fri Jan 20 08:07:53 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Jan 20 08:07:53 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Fri Jan 20 12:02:24 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0030.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 12:02:24 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Fri Jan 20 12:02:24 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 12:02:24 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Fri Jan 20 12:02:24 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Fri Jan 20 12:02:24 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0030.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Fri Jan 20 12:02:24 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 12:02:25 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Fri Jan 20 12:02:25 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Fri Jan 20 12:02:25 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 12:02:25 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Fri Jan 20 12:02:25 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Jan 20 12:02:25 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Fri Jan 20 12:02:25 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Jan 20 12:02:25 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0030.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 12:02:25 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Jan 20 12:02:25 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 12:02:25 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Jan 20 12:02:25 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 12:02:25 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Jan 20 12:02:25 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Fri Jan 20 12:02:25 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Fri Jan 20 12:02:26 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Jan 20 12:02:26 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Fri Jan 20 16:01:00 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0031.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 16:01:00 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Fri Jan 20 16:01:00 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 16:01:00 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Fri Jan 20 16:01:00 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Fri Jan 20 16:01:00 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0031.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Fri Jan 20 16:01:00 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 16:01:00 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Fri Jan 20 16:01:00 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Fri Jan 20 16:01:00 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 16:01:00 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Fri Jan 20 16:01:00 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Jan 20 16:01:00 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Fri Jan 20 16:01:00 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Jan 20 16:01:00 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0031.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 16:01:00 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Jan 20 16:01:00 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 16:01:00 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Jan 20 16:01:00 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 16:01:00 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Jan 20 16:01:00 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Fri Jan 20 16:01:01 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Fri Jan 20 16:01:01 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Jan 20 16:01:01 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Fri Jan 20 20:00:57 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0032.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 20:00:57 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Fri Jan 20 20:00:57 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 20:00:57 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Fri Jan 20 20:00:57 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Fri Jan 20 20:00:57 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0032.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Fri Jan 20 20:00:57 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 20:00:57 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Fri Jan 20 20:00:57 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Fri Jan 20 20:00:57 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 20:00:57 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Fri Jan 20 20:00:57 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Jan 20 20:00:57 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Fri Jan 20 20:00:57 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Jan 20 20:00:57 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0032.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 20:00:57 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Jan 20 20:00:58 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 20:00:58 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Jan 20 20:00:58 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 20:00:58 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Jan 20 20:00:58 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Fri Jan 20 20:00:58 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Fri Jan 20 20:00:58 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Jan 20 20:00:58 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Sat Jan 21 08:04:10 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0033.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 08:04:11 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Sat Jan 21 08:04:11 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 08:04:11 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Sat Jan 21 08:04:11 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Sat Jan 21 08:04:11 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0033.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Sat Jan 21 08:04:11 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 08:04:11 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Sat Jan 21 08:04:11 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Sat Jan 21 08:04:11 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 08:04:11 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Sat Jan 21 08:04:11 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Jan 21 08:04:11 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sat Jan 21 08:04:12 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Jan 21 08:04:12 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0033.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 08:04:12 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Jan 21 08:04:12 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 08:04:12 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Jan 21 08:04:12 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 08:04:12 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Jan 21 08:04:12 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Sat Jan 21 08:04:12 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sat Jan 21 08:04:12 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Jan 21 08:04:12 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Sat Jan 21 12:01:11 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0034.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 12:01:11 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Sat Jan 21 12:01:11 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 12:01:11 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Sat Jan 21 12:01:11 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Sat Jan 21 12:01:11 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0034.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Sat Jan 21 12:01:11 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 12:01:11 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Sat Jan 21 12:01:11 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Sat Jan 21 12:01:11 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 12:01:11 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Sat Jan 21 12:01:11 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Jan 21 12:01:11 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sat Jan 21 12:01:11 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Jan 21 12:01:11 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0034.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 12:01:11 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Jan 21 12:01:11 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 12:01:11 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Jan 21 12:01:11 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 12:01:11 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Jan 21 12:01:11 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Sat Jan 21 12:01:11 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sat Jan 21 12:01:11 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Jan 21 12:01:11 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Sat Jan 21 16:00:58 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0035.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 16:00:59 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Sat Jan 21 16:00:59 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 16:00:59 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Sat Jan 21 16:00:59 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Sat Jan 21 16:00:59 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0035.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Sat Jan 21 16:00:59 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 16:00:59 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Sat Jan 21 16:00:59 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Sat Jan 21 16:00:59 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 16:00:59 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Sat Jan 21 16:00:59 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Jan 21 16:00:59 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sat Jan 21 16:00:59 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Jan 21 16:00:59 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0035.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 16:00:59 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Jan 21 16:00:59 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 16:00:59 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Jan 21 16:00:59 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 16:00:59 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Jan 21 16:00:59 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Sat Jan 21 16:00:59 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sat Jan 21 16:00:59 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Jan 21 16:00:59 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Sat Jan 21 20:00:57 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0036.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 20:00:57 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Sat Jan 21 20:00:57 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 20:00:57 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Sat Jan 21 20:00:57 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Sat Jan 21 20:00:57 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0036.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Sat Jan 21 20:00:57 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 20:00:57 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Sat Jan 21 20:00:57 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Sat Jan 21 20:00:57 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 20:00:57 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Sat Jan 21 20:00:57 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Jan 21 20:00:57 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sat Jan 21 20:00:57 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Jan 21 20:00:57 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0036.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 20:00:57 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Jan 21 20:00:57 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 20:00:57 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Jan 21 20:00:57 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 20:00:57 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Jan 21 20:00:57 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Sat Jan 21 20:00:57 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sat Jan 21 20:00:57 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Jan 21 20:00:57 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Sun Jan 22 08:03:01 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0037.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 08:03:01 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Sun Jan 22 08:03:01 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 08:03:01 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Sun Jan 22 08:03:01 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Sun Jan 22 08:03:01 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0037.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Sun Jan 22 08:03:01 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 08:03:01 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Sun Jan 22 08:03:01 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Sun Jan 22 08:03:01 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 08:03:01 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Sun Jan 22 08:03:01 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Jan 22 08:03:02 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sun Jan 22 08:03:02 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Jan 22 08:03:02 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0037.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 08:03:02 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Jan 22 08:03:02 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 08:03:02 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Jan 22 08:03:02 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 08:03:02 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Jan 22 08:03:02 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Sun Jan 22 08:03:02 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sun Jan 22 08:03:02 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Jan 22 08:03:02 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Sun Jan 22 12:01:00 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0038.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 12:01:00 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Sun Jan 22 12:01:00 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 12:01:00 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Sun Jan 22 12:01:00 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Sun Jan 22 12:01:00 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0038.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Sun Jan 22 12:01:00 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 12:01:00 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Sun Jan 22 12:01:00 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Sun Jan 22 12:01:00 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 12:01:00 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Sun Jan 22 12:01:00 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Jan 22 12:01:00 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sun Jan 22 12:01:00 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Jan 22 12:01:00 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0038.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 12:01:00 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Jan 22 12:01:00 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 12:01:00 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Jan 22 12:01:00 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 12:01:00 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Jan 22 12:01:00 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Sun Jan 22 12:01:00 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sun Jan 22 12:01:00 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Jan 22 12:01:00 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Sun Jan 22 16:01:34 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0039.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 16:01:34 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Sun Jan 22 16:01:34 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 16:01:34 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Sun Jan 22 16:01:35 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Sun Jan 22 16:01:35 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0039.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Sun Jan 22 16:01:35 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 16:01:35 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Sun Jan 22 16:01:35 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Sun Jan 22 16:01:35 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 16:01:35 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Sun Jan 22 16:01:35 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Jan 22 16:01:35 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sun Jan 22 16:01:35 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Jan 22 16:01:35 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0039.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 16:01:35 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Jan 22 16:01:35 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 16:01:35 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Jan 22 16:01:35 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 16:01:35 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Jan 22 16:01:35 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Sun Jan 22 16:01:35 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sun Jan 22 16:01:35 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Jan 22 16:01:35 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Sun Jan 22 20:01:29 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0040.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 20:01:29 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Sun Jan 22 20:01:29 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 20:01:29 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Sun Jan 22 20:01:29 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Sun Jan 22 20:01:29 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0040.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Sun Jan 22 20:01:29 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 20:01:29 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Sun Jan 22 20:01:29 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Sun Jan 22 20:01:29 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 20:01:29 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Sun Jan 22 20:01:29 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Jan 22 20:01:29 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sun Jan 22 20:01:30 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Jan 22 20:01:30 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0040.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 20:01:30 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Jan 22 20:01:30 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 20:01:30 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Jan 22 20:01:30 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 20:01:30 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Jan 22 20:01:30 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Sun Jan 22 20:01:30 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sun Jan 22 20:01:30 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Jan 22 20:01:30 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Mon Jan 23 08:02:58 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0041.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 08:02:58 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Mon Jan 23 08:02:58 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 08:02:58 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Mon Jan 23 08:02:58 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Mon Jan 23 08:02:58 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0041.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Mon Jan 23 08:02:58 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 08:02:58 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Mon Jan 23 08:02:58 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Mon Jan 23 08:02:58 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 08:02:58 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Mon Jan 23 08:02:58 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Jan 23 08:02:58 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Mon Jan 23 08:02:58 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Jan 23 08:02:58 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0041.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 08:02:58 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Jan 23 08:02:58 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 08:02:58 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Jan 23 08:02:58 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 08:02:58 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Jan 23 08:02:58 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Mon Jan 23 08:02:58 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Mon Jan 23 08:02:58 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Jan 23 08:02:59 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Mon Jan 23 12:01:06 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0042.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 12:01:06 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Mon Jan 23 12:01:06 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 12:01:06 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Mon Jan 23 12:01:06 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Mon Jan 23 12:01:06 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0042.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Mon Jan 23 12:01:06 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 12:01:06 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Mon Jan 23 12:01:06 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Mon Jan 23 12:01:06 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 12:01:06 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Mon Jan 23 12:01:06 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Jan 23 12:01:06 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Mon Jan 23 12:01:06 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Jan 23 12:01:06 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0042.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 12:01:06 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Jan 23 12:01:06 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 12:01:06 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Jan 23 12:01:06 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 12:01:06 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Jan 23 12:01:06 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Mon Jan 23 12:01:06 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Mon Jan 23 12:01:06 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Jan 23 12:01:06 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Mon Jan 23 16:02:08 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0043.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 16:02:08 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Mon Jan 23 16:02:08 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 16:02:08 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Mon Jan 23 16:02:08 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Mon Jan 23 16:02:08 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0043.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Mon Jan 23 16:02:08 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 16:02:08 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Mon Jan 23 16:02:08 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Mon Jan 23 16:02:08 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 16:02:08 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Mon Jan 23 16:02:08 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Jan 23 16:02:08 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Mon Jan 23 16:02:09 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Jan 23 16:02:09 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0043.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 16:02:09 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Jan 23 16:02:09 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 16:02:09 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Jan 23 16:02:09 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 16:02:09 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Jan 23 16:02:09 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Mon Jan 23 16:02:09 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Mon Jan 23 16:02:09 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Jan 23 16:02:09 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Mon Jan 23 20:00:59 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0044.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 20:01:01 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Mon Jan 23 20:01:01 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 20:01:01 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Mon Jan 23 20:01:01 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Mon Jan 23 20:01:01 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0044.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Mon Jan 23 20:01:02 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 20:01:02 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Mon Jan 23 20:01:02 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Mon Jan 23 20:01:02 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 20:01:02 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Mon Jan 23 20:01:02 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Jan 23 20:01:02 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Mon Jan 23 20:01:02 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Jan 23 20:01:02 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0044.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 20:01:02 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Jan 23 20:01:02 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 20:01:02 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Jan 23 20:01:02 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 20:01:02 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Jan 23 20:01:02 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Mon Jan 23 20:01:02 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Mon Jan 23 20:01:02 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Jan 23 20:01:02 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Tue Jan 24 08:03:30 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0045.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 08:03:30 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Tue Jan 24 08:03:30 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 08:03:30 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Tue Jan 24 08:03:30 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Tue Jan 24 08:03:30 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0045.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Tue Jan 24 08:03:30 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 08:03:30 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Tue Jan 24 08:03:30 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Tue Jan 24 08:03:30 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 08:03:30 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Tue Jan 24 08:03:30 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Jan 24 08:03:30 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Tue Jan 24 08:03:30 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Jan 24 08:03:31 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0045.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 08:03:31 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Jan 24 08:03:31 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 08:03:31 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Jan 24 08:03:31 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 08:03:31 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Jan 24 08:03:31 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Tue Jan 24 08:03:31 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Tue Jan 24 08:03:31 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Jan 24 08:03:31 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Tue Jan 24 12:03:34 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0046.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 12:03:34 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Tue Jan 24 12:03:34 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 12:03:34 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Tue Jan 24 12:03:34 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Tue Jan 24 12:03:35 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0046.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Tue Jan 24 12:03:35 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 12:03:35 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Tue Jan 24 12:03:35 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Tue Jan 24 12:03:35 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 12:03:35 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Tue Jan 24 12:03:35 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Jan 24 12:03:35 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Tue Jan 24 12:03:35 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Jan 24 12:03:36 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0046.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 12:03:36 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Jan 24 12:03:36 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 12:03:36 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Jan 24 12:03:36 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 12:03:36 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Jan 24 12:03:36 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Tue Jan 24 12:03:36 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Tue Jan 24 12:03:37 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Jan 24 12:03:37 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Tue Jan 24 16:01:39 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0047.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 16:01:39 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Tue Jan 24 16:01:39 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 16:01:39 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Tue Jan 24 16:01:39 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Tue Jan 24 16:01:39 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0047.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Tue Jan 24 16:01:39 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 16:01:39 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Tue Jan 24 16:01:39 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Tue Jan 24 16:01:39 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 16:01:39 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Tue Jan 24 16:01:39 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Jan 24 16:01:39 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Tue Jan 24 16:01:40 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Jan 24 16:01:40 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0047.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 16:01:40 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Jan 24 16:01:40 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 16:01:40 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Jan 24 16:01:40 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 16:01:40 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Jan 24 16:01:40 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Tue Jan 24 16:01:40 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Tue Jan 24 16:01:40 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Jan 24 16:01:40 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Tue Jan 24 20:02:07 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0048.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 20:02:07 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Tue Jan 24 20:02:07 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 20:02:07 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Tue Jan 24 20:02:07 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Tue Jan 24 20:02:07 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0048.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Tue Jan 24 20:02:07 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 20:02:07 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Tue Jan 24 20:02:07 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Tue Jan 24 20:02:07 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 20:02:07 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Tue Jan 24 20:02:07 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Jan 24 20:02:07 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Tue Jan 24 20:02:07 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Jan 24 20:02:08 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0048.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 20:02:08 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Jan 24 20:02:08 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 20:02:08 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Jan 24 20:02:08 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 20:02:08 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Jan 24 20:02:08 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Tue Jan 24 20:02:08 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Tue Jan 24 20:02:08 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Jan 24 20:02:08 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Wed Jan 25 08:02:20 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0049.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 08:02:20 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Wed Jan 25 08:02:20 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 08:02:20 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Wed Jan 25 08:02:20 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Wed Jan 25 08:02:20 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0049.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Wed Jan 25 08:02:20 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 08:02:20 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Wed Jan 25 08:02:20 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Wed Jan 25 08:02:20 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 08:02:20 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Wed Jan 25 08:02:20 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Jan 25 08:02:20 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Wed Jan 25 08:02:21 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Jan 25 08:02:21 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0049.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 08:02:21 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Jan 25 08:02:21 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 08:02:21 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Jan 25 08:02:21 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 08:02:21 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Jan 25 08:02:21 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Wed Jan 25 08:02:21 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Wed Jan 25 08:02:21 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Jan 25 08:02:21 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Wed Jan 25 12:01:15 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0050.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 12:01:15 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Wed Jan 25 12:01:15 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 12:01:15 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Wed Jan 25 12:01:15 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Wed Jan 25 12:01:15 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0050.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Wed Jan 25 12:01:15 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 12:01:15 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Wed Jan 25 12:01:15 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Wed Jan 25 12:01:15 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 12:01:15 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Wed Jan 25 12:01:15 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Jan 25 12:01:15 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Wed Jan 25 12:01:15 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Jan 25 12:01:15 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0050.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 12:01:15 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Jan 25 12:01:15 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 12:01:15 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Jan 25 12:01:16 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 12:01:16 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Jan 25 12:01:16 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Wed Jan 25 12:01:16 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Wed Jan 25 12:01:16 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Jan 25 12:01:16 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Wed Jan 25 16:01:13 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0051.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 16:01:13 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Wed Jan 25 16:01:13 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 16:01:13 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Wed Jan 25 16:01:13 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Wed Jan 25 16:01:13 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0051.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Wed Jan 25 16:01:13 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 16:01:13 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Wed Jan 25 16:01:13 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Wed Jan 25 16:01:13 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 16:01:13 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Wed Jan 25 16:01:13 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Jan 25 16:01:14 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Wed Jan 25 16:01:14 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Jan 25 16:01:14 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0051.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 16:01:14 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Jan 25 16:01:14 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 16:01:14 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Jan 25 16:01:14 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 16:01:14 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Jan 25 16:01:14 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Wed Jan 25 16:01:14 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Wed Jan 25 16:01:14 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Jan 25 16:01:14 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Wed Jan 25 20:01:05 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0052.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 20:01:05 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Wed Jan 25 20:01:05 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 20:01:05 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Wed Jan 25 20:01:05 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Wed Jan 25 20:01:05 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0052.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Wed Jan 25 20:01:05 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 20:01:05 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Wed Jan 25 20:01:05 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Wed Jan 25 20:01:05 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 20:01:05 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Wed Jan 25 20:01:06 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Jan 25 20:01:06 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Wed Jan 25 20:01:06 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Jan 25 20:01:06 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0052.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 20:01:06 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Jan 25 20:01:06 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 20:01:06 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Jan 25 20:01:06 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 20:01:06 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Jan 25 20:01:06 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Wed Jan 25 20:01:06 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Wed Jan 25 20:01:06 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Jan 25 20:01:06 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Thu Jan 26 08:06:35 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0053.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 08:06:35 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Thu Jan 26 08:06:35 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 08:06:35 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Thu Jan 26 08:06:35 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Thu Jan 26 08:06:38 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0053.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Thu Jan 26 08:06:38 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 08:06:38 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Thu Jan 26 08:06:38 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Thu Jan 26 08:06:38 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 08:06:38 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Thu Jan 26 08:06:38 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Thu Jan 26 08:06:39 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Thu Jan 26 08:06:39 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Thu Jan 26 08:06:39 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0053.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 08:06:39 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Thu Jan 26 08:06:39 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 08:06:39 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Thu Jan 26 08:06:39 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 08:06:39 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Thu Jan 26 08:06:40 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Thu Jan 26 08:06:40 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Thu Jan 26 08:06:40 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Thu Jan 26 08:06:40 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Thu Jan 26 12:01:19 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0054.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 12:01:19 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Thu Jan 26 12:01:19 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 12:01:19 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Thu Jan 26 12:01:19 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Thu Jan 26 12:01:19 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0054.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Thu Jan 26 12:01:19 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 12:01:19 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Thu Jan 26 12:01:19 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Thu Jan 26 12:01:19 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 12:01:19 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Thu Jan 26 12:01:19 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Thu Jan 26 12:01:19 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Thu Jan 26 12:01:19 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Thu Jan 26 12:01:19 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0054.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 12:01:19 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Thu Jan 26 12:01:19 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 12:01:19 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Thu Jan 26 12:01:19 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 12:01:20 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Thu Jan 26 12:01:20 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Thu Jan 26 12:01:20 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Thu Jan 26 12:01:20 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Thu Jan 26 12:01:20 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Thu Jan 26 16:01:02 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0055.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 16:01:02 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Thu Jan 26 16:01:02 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 16:01:02 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Thu Jan 26 16:01:02 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Thu Jan 26 16:01:02 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0055.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Thu Jan 26 16:01:02 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 16:01:02 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Thu Jan 26 16:01:02 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Thu Jan 26 16:01:02 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 16:01:02 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Thu Jan 26 16:01:02 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Thu Jan 26 16:01:02 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Thu Jan 26 16:01:02 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Thu Jan 26 16:01:02 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0055.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 16:01:02 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Thu Jan 26 16:01:02 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 16:01:02 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Thu Jan 26 16:01:02 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 16:01:02 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Thu Jan 26 16:01:02 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Thu Jan 26 16:01:02 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Thu Jan 26 16:01:02 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Thu Jan 26 16:01:02 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Thu Jan 26 20:00:54 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0056.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 20:00:54 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Thu Jan 26 20:00:54 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 20:00:54 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Thu Jan 26 20:00:54 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Thu Jan 26 20:00:54 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0056.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Thu Jan 26 20:00:54 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 20:00:54 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Thu Jan 26 20:00:54 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Thu Jan 26 20:00:55 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 20:00:55 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Thu Jan 26 20:00:55 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Thu Jan 26 20:00:55 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Thu Jan 26 20:00:55 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Thu Jan 26 20:00:55 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0056.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 20:00:55 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Thu Jan 26 20:00:55 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 20:00:55 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Thu Jan 26 20:00:55 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 20:00:55 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Thu Jan 26 20:00:55 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Thu Jan 26 20:00:55 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Thu Jan 26 20:00:55 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Thu Jan 26 20:00:55 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Fri Jan 27 08:07:34 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0057.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 08:07:34 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Fri Jan 27 08:07:34 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 08:07:34 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Fri Jan 27 08:07:34 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Fri Jan 27 08:07:37 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0057.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Fri Jan 27 08:07:37 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 08:07:37 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Fri Jan 27 08:07:37 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Fri Jan 27 08:07:37 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 08:07:37 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Fri Jan 27 08:07:37 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Jan 27 08:07:37 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Fri Jan 27 08:07:37 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Jan 27 08:07:38 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0057.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 08:07:38 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Jan 27 08:07:38 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 08:07:38 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Jan 27 08:07:38 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 08:07:38 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Jan 27 08:07:38 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Fri Jan 27 08:07:38 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Fri Jan 27 08:07:38 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Jan 27 08:07:38 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Fri Jan 27 12:02:24 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0058.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 12:02:24 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Fri Jan 27 12:02:24 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 12:02:24 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Fri Jan 27 12:02:24 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Fri Jan 27 12:02:24 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0058.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Fri Jan 27 12:02:24 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 12:02:24 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Fri Jan 27 12:02:24 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Fri Jan 27 12:02:24 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 12:02:24 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Fri Jan 27 12:02:24 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Jan 27 12:02:24 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Fri Jan 27 12:02:25 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Jan 27 12:02:25 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0058.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 12:02:25 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Jan 27 12:02:25 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 12:02:25 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Jan 27 12:02:25 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 12:02:25 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Jan 27 12:02:25 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Fri Jan 27 12:02:25 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Fri Jan 27 12:02:25 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Jan 27 12:02:25 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Fri Jan 27 16:01:16 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0059.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 16:01:16 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Fri Jan 27 16:01:16 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 16:01:16 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Fri Jan 27 16:01:16 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Fri Jan 27 16:01:16 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0059.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Fri Jan 27 16:01:16 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 16:01:16 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Fri Jan 27 16:01:16 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Fri Jan 27 16:01:16 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 16:01:17 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Fri Jan 27 16:01:17 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Jan 27 16:01:17 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Fri Jan 27 16:01:17 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Jan 27 16:01:17 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0059.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 16:01:17 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Jan 27 16:01:17 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 16:01:17 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Jan 27 16:01:17 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 16:01:18 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Jan 27 16:01:18 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Fri Jan 27 16:01:18 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Fri Jan 27 16:01:18 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Jan 27 16:01:18 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Fri Jan 27 20:01:08 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0060.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 20:01:08 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Fri Jan 27 20:01:08 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 20:01:08 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Fri Jan 27 20:01:08 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Fri Jan 27 20:01:08 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0060.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Fri Jan 27 20:01:08 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 20:01:08 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Fri Jan 27 20:01:09 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Fri Jan 27 20:01:09 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 20:01:09 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Fri Jan 27 20:01:09 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Jan 27 20:01:09 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Fri Jan 27 20:01:09 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Jan 27 20:01:09 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0060.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 20:01:09 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Jan 27 20:01:09 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 20:01:09 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Jan 27 20:01:09 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 20:01:09 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Jan 27 20:01:09 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Fri Jan 27 20:01:09 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Fri Jan 27 20:01:09 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Jan 27 20:01:09 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Sat Jan 28 08:06:14 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0061.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 08:06:15 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Sat Jan 28 08:06:15 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 08:06:15 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Sat Jan 28 08:06:15 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Sat Jan 28 08:06:16 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0061.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Sat Jan 28 08:06:16 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 08:06:16 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Sat Jan 28 08:06:16 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Sat Jan 28 08:06:16 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 08:06:16 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Sat Jan 28 08:06:16 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Jan 28 08:06:16 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sat Jan 28 08:06:16 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Jan 28 08:06:17 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0061.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 08:06:17 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Jan 28 08:06:17 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 08:06:17 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Jan 28 08:06:17 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 08:06:17 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Jan 28 08:06:17 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Sat Jan 28 08:06:17 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sat Jan 28 08:06:17 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Jan 28 08:06:18 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Sat Jan 28 12:02:04 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0062.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 12:02:04 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Sat Jan 28 12:02:04 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 12:02:04 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Sat Jan 28 12:02:04 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Sat Jan 28 12:02:04 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0062.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Sat Jan 28 12:02:04 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 12:02:04 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Sat Jan 28 12:02:04 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Sat Jan 28 12:02:05 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 12:02:05 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Sat Jan 28 12:02:05 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Jan 28 12:02:05 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sat Jan 28 12:02:05 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Jan 28 12:02:06 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0062.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 12:02:06 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Jan 28 12:02:06 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 12:02:06 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Jan 28 12:02:06 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 12:02:06 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Jan 28 12:02:06 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Sat Jan 28 12:02:06 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sat Jan 28 12:02:06 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Jan 28 12:02:06 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Sat Jan 28 16:01:05 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0063.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 16:01:05 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Sat Jan 28 16:01:05 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 16:01:05 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Sat Jan 28 16:01:05 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Sat Jan 28 16:01:05 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0063.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Sat Jan 28 16:01:05 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 16:01:05 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Sat Jan 28 16:01:05 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Sat Jan 28 16:01:05 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 16:01:05 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Sat Jan 28 16:01:05 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Jan 28 16:01:05 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sat Jan 28 16:01:05 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Jan 28 16:01:05 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0063.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 16:01:05 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Jan 28 16:01:05 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 16:01:05 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Jan 28 16:01:05 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 16:01:05 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Jan 28 16:01:05 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Sat Jan 28 16:01:05 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sat Jan 28 16:01:05 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Jan 28 16:01:05 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Sat Jan 28 20:01:04 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0064.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 20:01:04 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Sat Jan 28 20:01:04 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 20:01:04 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Sat Jan 28 20:01:04 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Sat Jan 28 20:01:04 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0064.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Sat Jan 28 20:01:04 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 20:01:04 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Sat Jan 28 20:01:04 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Sat Jan 28 20:01:04 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 20:01:04 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Sat Jan 28 20:01:04 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Jan 28 20:01:04 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sat Jan 28 20:01:04 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Jan 28 20:01:04 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0064.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 20:01:04 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Jan 28 20:01:04 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 20:01:04 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Jan 28 20:01:04 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 20:01:04 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Jan 28 20:01:04 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Sat Jan 28 20:01:04 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sat Jan 28 20:01:04 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Jan 28 20:01:04 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Sun Jan 29 08:07:51 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0065.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 08:07:51 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Sun Jan 29 08:07:51 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 08:07:51 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Sun Jan 29 08:07:51 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Sun Jan 29 08:07:52 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0065.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Sun Jan 29 08:07:52 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 08:07:52 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Sun Jan 29 08:07:52 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Sun Jan 29 08:07:52 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 08:07:52 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Sun Jan 29 08:07:52 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Jan 29 08:07:52 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sun Jan 29 08:07:52 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Jan 29 08:07:52 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0065.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 08:07:52 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Jan 29 08:07:52 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 08:07:52 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Jan 29 08:07:52 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 08:07:52 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Jan 29 08:07:52 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Sun Jan 29 08:07:52 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sun Jan 29 08:07:52 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Jan 29 08:07:52 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Sun Jan 29 12:01:14 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0066.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 12:01:14 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Sun Jan 29 12:01:14 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 12:01:15 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Sun Jan 29 12:01:15 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Sun Jan 29 12:01:15 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0066.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Sun Jan 29 12:01:15 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 12:01:15 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Sun Jan 29 12:01:15 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Sun Jan 29 12:01:15 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 12:01:15 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Sun Jan 29 12:01:15 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Jan 29 12:01:15 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sun Jan 29 12:01:15 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Jan 29 12:01:15 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0066.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 12:01:15 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Jan 29 12:01:15 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 12:01:15 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Jan 29 12:01:15 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 12:01:15 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Jan 29 12:01:15 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Sun Jan 29 12:01:15 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sun Jan 29 12:01:15 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Jan 29 12:01:15 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Sun Jan 29 16:01:02 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0067.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 16:01:02 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Sun Jan 29 16:01:02 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 16:01:02 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Sun Jan 29 16:01:02 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Sun Jan 29 16:01:02 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0067.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Sun Jan 29 16:01:02 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 16:01:02 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Sun Jan 29 16:01:02 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Sun Jan 29 16:01:02 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 16:01:02 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Sun Jan 29 16:01:02 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Jan 29 16:01:02 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sun Jan 29 16:01:02 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Jan 29 16:01:02 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0067.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 16:01:02 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Jan 29 16:01:02 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 16:01:02 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Jan 29 16:01:02 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 16:01:02 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Jan 29 16:01:02 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Sun Jan 29 16:01:02 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sun Jan 29 16:01:02 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Jan 29 16:01:02 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Sun Jan 29 20:01:06 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0068.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 20:01:06 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Sun Jan 29 20:01:06 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 20:01:06 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Sun Jan 29 20:01:06 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Sun Jan 29 20:01:06 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0068.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Sun Jan 29 20:01:06 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 20:01:06 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Sun Jan 29 20:01:06 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Sun Jan 29 20:01:06 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 20:01:06 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Sun Jan 29 20:01:06 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Jan 29 20:01:06 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sun Jan 29 20:01:06 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Jan 29 20:01:06 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0068.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 20:01:06 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Jan 29 20:01:06 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 20:01:06 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Jan 29 20:01:07 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 20:01:07 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Jan 29 20:01:07 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Sun Jan 29 20:01:07 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sun Jan 29 20:01:07 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Jan 29 20:01:07 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Mon Jan 30 08:10:11 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0069.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 08:10:12 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Mon Jan 30 08:10:12 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 08:10:12 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Mon Jan 30 08:10:12 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Mon Jan 30 08:10:14 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0069.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Mon Jan 30 08:10:14 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 08:10:14 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Mon Jan 30 08:10:14 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Mon Jan 30 08:10:14 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 08:10:14 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Mon Jan 30 08:10:14 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Jan 30 08:10:14 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Mon Jan 30 08:10:14 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Jan 30 08:10:15 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0069.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 08:10:15 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Jan 30 08:10:15 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 08:10:15 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Jan 30 08:10:15 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 08:10:15 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Jan 30 08:10:15 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Mon Jan 30 08:10:15 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Mon Jan 30 08:10:15 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Jan 30 08:10:15 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Mon Jan 30 12:04:17 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0070.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 12:04:17 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Mon Jan 30 12:04:17 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 12:04:17 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Mon Jan 30 12:04:17 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Mon Jan 30 12:04:18 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0070.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Mon Jan 30 12:04:18 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 12:04:18 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Mon Jan 30 12:04:18 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Mon Jan 30 12:04:18 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 12:04:18 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Mon Jan 30 12:04:18 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Jan 30 12:04:18 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Mon Jan 30 12:04:18 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Jan 30 12:04:18 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0070.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 12:04:18 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Jan 30 12:04:18 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 12:04:18 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Jan 30 12:04:18 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 12:04:18 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Jan 30 12:04:18 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Mon Jan 30 12:04:18 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Mon Jan 30 12:04:18 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Jan 30 12:04:19 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Mon Jan 30 16:04:34 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0071.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 16:04:34 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Mon Jan 30 16:04:34 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 16:04:34 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Mon Jan 30 16:04:34 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Mon Jan 30 16:04:35 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0071.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Mon Jan 30 16:04:35 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 16:04:35 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Mon Jan 30 16:04:35 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Mon Jan 30 16:04:35 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 16:04:35 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Mon Jan 30 16:04:35 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Jan 30 16:04:35 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Mon Jan 30 16:04:35 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Jan 30 16:04:35 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0071.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 16:04:35 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Jan 30 16:04:35 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 16:04:35 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Jan 30 16:04:35 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 16:04:35 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Jan 30 16:04:35 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Mon Jan 30 16:04:35 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Mon Jan 30 16:04:35 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Jan 30 16:04:35 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Mon Jan 30 20:02:31 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0072.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 20:02:31 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Mon Jan 30 20:02:31 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 20:02:31 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Mon Jan 30 20:02:31 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Mon Jan 30 20:02:32 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0072.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Mon Jan 30 20:02:32 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 20:02:32 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Mon Jan 30 20:02:32 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Mon Jan 30 20:02:32 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 20:02:32 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Mon Jan 30 20:02:32 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Jan 30 20:02:32 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Mon Jan 30 20:02:32 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Jan 30 20:02:32 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0072.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 20:02:32 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Jan 30 20:02:32 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 20:02:32 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Jan 30 20:02:32 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 20:02:32 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Jan 30 20:02:32 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Mon Jan 30 20:02:32 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Mon Jan 30 20:02:32 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Jan 30 20:02:32 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Tue Jan 31 08:08:30 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0073.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 08:08:30 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Tue Jan 31 08:08:30 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 08:08:30 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Tue Jan 31 08:08:30 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Tue Jan 31 08:08:32 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0073.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Tue Jan 31 08:08:32 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 08:08:32 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Tue Jan 31 08:08:32 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Tue Jan 31 08:08:32 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 08:08:32 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Tue Jan 31 08:08:32 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Jan 31 08:08:32 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Tue Jan 31 08:08:32 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Jan 31 08:08:32 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0073.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 08:08:32 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Jan 31 08:08:32 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 08:08:32 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Jan 31 08:08:32 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 08:08:32 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Jan 31 08:08:32 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Tue Jan 31 08:08:32 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Tue Jan 31 08:08:32 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Jan 31 08:08:32 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Tue Jan 31 12:04:44 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0074.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 12:04:44 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Tue Jan 31 12:04:44 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 12:04:44 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Tue Jan 31 12:04:44 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Tue Jan 31 12:04:46 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0074.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Tue Jan 31 12:04:46 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 12:04:46 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Tue Jan 31 12:04:46 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Tue Jan 31 12:04:46 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 12:04:46 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Tue Jan 31 12:04:46 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Jan 31 12:04:46 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Tue Jan 31 12:04:46 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Jan 31 12:04:46 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0074.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 12:04:46 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Jan 31 12:04:46 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 12:04:46 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Jan 31 12:04:46 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 12:04:46 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Jan 31 12:04:46 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Tue Jan 31 12:04:46 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Tue Jan 31 12:04:46 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Jan 31 12:04:46 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Tue Jan 31 16:02:39 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0075.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 16:02:40 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Tue Jan 31 16:02:40 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 16:02:40 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Tue Jan 31 16:02:40 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Tue Jan 31 16:02:40 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0075.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Tue Jan 31 16:02:41 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 16:02:41 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Tue Jan 31 16:02:41 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Tue Jan 31 16:02:41 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 16:02:41 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Tue Jan 31 16:02:41 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Jan 31 16:02:41 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Tue Jan 31 16:02:41 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Jan 31 16:02:41 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0075.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 16:02:41 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Jan 31 16:02:41 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 16:02:41 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Jan 31 16:02:41 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 16:02:41 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Jan 31 16:02:41 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Tue Jan 31 16:02:41 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Tue Jan 31 16:02:41 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Jan 31 16:02:41 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Tue Jan 31 20:01:20 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0076.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 20:01:20 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Tue Jan 31 20:01:20 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 20:01:20 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Tue Jan 31 20:01:20 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Tue Jan 31 20:01:20 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0076.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Tue Jan 31 20:01:20 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 20:01:20 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Tue Jan 31 20:01:20 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Tue Jan 31 20:01:20 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 20:01:20 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Tue Jan 31 20:01:20 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Jan 31 20:01:20 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Tue Jan 31 20:01:20 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Jan 31 20:01:20 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0076.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 20:01:20 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Jan 31 20:01:20 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 20:01:20 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Jan 31 20:01:20 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 20:01:20 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Jan 31 20:01:20 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Tue Jan 31 20:01:20 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Tue Jan 31 20:01:20 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Jan 31 20:01:20 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Wed Feb 1 08:10:49 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0077.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 08:10:49 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Wed Feb 1 08:10:49 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 08:10:49 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Wed Feb 1 08:10:49 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Wed Feb 1 08:10:51 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0077.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Wed Feb 1 08:10:51 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 08:10:51 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Wed Feb 1 08:10:51 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Wed Feb 1 08:10:51 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 08:10:51 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Wed Feb 1 08:10:52 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Feb 1 08:10:52 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Wed Feb 1 08:10:52 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Feb 1 08:10:52 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0077.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 08:10:52 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Feb 1 08:10:52 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 08:10:52 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Feb 1 08:10:52 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 08:10:52 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Feb 1 08:10:52 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Wed Feb 1 08:10:52 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Wed Feb 1 08:10:52 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Feb 1 08:10:52 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Wed Feb 1 12:03:01 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0078.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 12:03:01 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Wed Feb 1 12:03:02 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 12:03:02 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Wed Feb 1 12:03:02 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Wed Feb 1 12:03:03 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0078.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Wed Feb 1 12:03:03 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 12:03:03 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Wed Feb 1 12:03:03 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Wed Feb 1 12:03:03 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 12:03:03 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Wed Feb 1 12:03:03 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Feb 1 12:03:03 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Wed Feb 1 12:03:03 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Feb 1 12:03:03 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0078.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 12:03:03 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Feb 1 12:03:03 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 12:03:03 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Feb 1 12:03:03 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 12:03:03 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Feb 1 12:03:03 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Wed Feb 1 12:03:03 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Wed Feb 1 12:03:03 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Feb 1 12:03:03 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Wed Feb 1 16:01:17 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0079.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 16:01:17 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Wed Feb 1 16:01:17 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 16:01:17 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Wed Feb 1 16:01:17 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Wed Feb 1 16:01:17 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0079.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Wed Feb 1 16:01:17 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 16:01:17 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Wed Feb 1 16:01:17 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Wed Feb 1 16:01:17 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 16:01:17 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Wed Feb 1 16:01:17 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Feb 1 16:01:17 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Wed Feb 1 16:01:17 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Feb 1 16:01:17 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0079.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 16:01:17 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Feb 1 16:01:17 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 16:01:17 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Feb 1 16:01:17 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 16:01:17 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Feb 1 16:01:17 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Wed Feb 1 16:01:17 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Wed Feb 1 16:01:17 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Feb 1 16:01:17 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Wed Feb 1 20:01:14 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0080.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 20:01:14 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Wed Feb 1 20:01:14 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 20:01:14 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Wed Feb 1 20:01:14 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Wed Feb 1 20:01:14 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0080.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Wed Feb 1 20:01:14 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 20:01:14 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Wed Feb 1 20:01:14 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Wed Feb 1 20:01:14 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 20:01:14 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Wed Feb 1 20:01:14 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Feb 1 20:01:14 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Wed Feb 1 20:01:14 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Feb 1 20:01:14 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0080.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 20:01:14 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Feb 1 20:01:14 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 20:01:14 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Feb 1 20:01:14 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 20:01:14 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Feb 1 20:01:14 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Wed Feb 1 20:01:14 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Wed Feb 1 20:01:14 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Feb 1 20:01:14 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Thu Feb 2 08:14:24 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0081.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 08:14:25 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Thu Feb 2 08:14:25 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 08:14:25 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Thu Feb 2 08:14:25 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Thu Feb 2 08:14:29 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0081.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Thu Feb 2 08:14:29 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 08:14:29 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Thu Feb 2 08:14:30 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Thu Feb 2 08:14:30 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 08:14:30 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Thu Feb 2 08:14:30 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Thu Feb 2 08:14:30 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Thu Feb 2 08:14:30 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Thu Feb 2 08:14:31 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0081.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 08:14:31 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Thu Feb 2 08:14:31 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 08:14:31 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Thu Feb 2 08:14:31 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 08:14:31 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Thu Feb 2 08:14:31 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Thu Feb 2 08:14:31 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Thu Feb 2 08:14:31 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Thu Feb 2 08:14:31 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Thu Feb 2 12:03:13 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0082.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 12:03:13 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Thu Feb 2 12:03:13 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 12:03:13 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Thu Feb 2 12:03:13 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Thu Feb 2 12:03:14 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0082.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Thu Feb 2 12:03:14 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 12:03:14 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Thu Feb 2 12:03:14 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Thu Feb 2 12:03:14 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 12:03:14 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Thu Feb 2 12:03:14 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Thu Feb 2 12:03:14 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Thu Feb 2 12:03:14 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Thu Feb 2 12:03:14 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0082.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 12:03:14 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Thu Feb 2 12:03:14 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 12:03:14 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Thu Feb 2 12:03:14 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 12:03:14 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Thu Feb 2 12:03:14 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Thu Feb 2 12:03:14 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Thu Feb 2 12:03:14 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Thu Feb 2 12:03:14 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Thu Feb 2 16:01:23 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0083.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 16:01:23 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Thu Feb 2 16:01:23 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 16:01:23 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Thu Feb 2 16:01:23 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Thu Feb 2 16:01:23 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0083.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Thu Feb 2 16:01:23 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 16:01:23 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Thu Feb 2 16:01:23 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Thu Feb 2 16:01:23 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 16:01:23 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Thu Feb 2 16:01:23 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Thu Feb 2 16:01:23 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Thu Feb 2 16:01:23 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Thu Feb 2 16:01:23 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0083.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 16:01:23 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Thu Feb 2 16:01:23 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 16:01:23 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Thu Feb 2 16:01:23 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 16:01:23 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Thu Feb 2 16:01:23 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Thu Feb 2 16:01:23 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Thu Feb 2 16:01:23 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Thu Feb 2 16:01:23 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Thu Feb 2 20:01:15 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0084.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 20:01:15 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Thu Feb 2 20:01:15 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 20:01:15 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Thu Feb 2 20:01:15 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Thu Feb 2 20:01:15 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0084.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Thu Feb 2 20:01:15 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 20:01:15 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Thu Feb 2 20:01:15 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Thu Feb 2 20:01:15 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 20:01:15 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Thu Feb 2 20:01:15 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Thu Feb 2 20:01:15 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Thu Feb 2 20:01:15 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Thu Feb 2 20:01:15 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0084.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 20:01:15 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Thu Feb 2 20:01:15 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 20:01:15 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Thu Feb 2 20:01:15 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 20:01:15 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Thu Feb 2 20:01:15 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Thu Feb 2 20:01:15 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Thu Feb 2 20:01:15 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Thu Feb 2 20:01:15 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Fri Feb 3 08:13:46 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0085.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 08:13:47 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Fri Feb 3 08:13:47 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 08:13:47 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Fri Feb 3 08:13:47 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Fri Feb 3 08:13:51 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0085.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Fri Feb 3 08:13:51 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 08:13:51 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Fri Feb 3 08:13:51 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Fri Feb 3 08:13:51 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 08:13:51 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Fri Feb 3 08:13:51 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Feb 3 08:13:51 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Fri Feb 3 08:13:52 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Feb 3 08:13:52 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0085.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 08:13:52 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Feb 3 08:13:52 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 08:13:52 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Feb 3 08:13:52 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 08:13:52 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Feb 3 08:13:52 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Fri Feb 3 08:13:52 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Fri Feb 3 08:13:52 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Feb 3 08:13:52 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Fri Feb 3 12:03:05 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0086.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 12:03:06 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Fri Feb 3 12:03:06 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 12:03:06 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Fri Feb 3 12:03:06 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Fri Feb 3 12:03:07 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0086.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Fri Feb 3 12:03:07 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 12:03:07 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Fri Feb 3 12:03:07 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Fri Feb 3 12:03:07 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 12:03:07 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Fri Feb 3 12:03:07 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Feb 3 12:03:07 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Fri Feb 3 12:03:08 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Feb 3 12:03:08 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0086.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 12:03:08 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Feb 3 12:03:08 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 12:03:08 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Feb 3 12:03:08 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 12:03:08 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Feb 3 12:03:08 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Fri Feb 3 12:03:08 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Fri Feb 3 12:03:08 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Feb 3 12:03:08 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Fri Feb 3 16:01:16 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0087.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 16:01:16 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Fri Feb 3 16:01:16 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 16:01:16 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Fri Feb 3 16:01:16 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Fri Feb 3 16:01:16 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0087.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Fri Feb 3 16:01:16 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 16:01:16 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Fri Feb 3 16:01:16 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Fri Feb 3 16:01:16 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 16:01:16 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Fri Feb 3 16:01:16 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Feb 3 16:01:16 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Fri Feb 3 16:01:16 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Feb 3 16:01:16 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0087.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 16:01:16 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Feb 3 16:01:16 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 16:01:16 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Feb 3 16:01:17 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 16:01:17 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Feb 3 16:01:17 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Fri Feb 3 16:01:17 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Fri Feb 3 16:01:17 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Feb 3 16:01:17 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Fri Feb 3 20:01:18 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0088.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 20:01:18 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Fri Feb 3 20:01:18 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 20:01:18 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Fri Feb 3 20:01:18 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Fri Feb 3 20:01:18 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0088.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Fri Feb 3 20:01:18 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 20:01:18 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Fri Feb 3 20:01:18 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Fri Feb 3 20:01:18 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 20:01:18 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Fri Feb 3 20:01:18 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Feb 3 20:01:18 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Fri Feb 3 20:01:18 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Feb 3 20:01:18 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0088.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 20:01:18 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Feb 3 20:01:18 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 20:01:18 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Feb 3 20:01:18 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 20:01:18 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Feb 3 20:01:18 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Fri Feb 3 20:01:18 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Fri Feb 3 20:01:18 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Feb 3 20:01:18 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Sat Feb 4 08:09:13 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0089.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 08:09:13 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Sat Feb 4 08:09:14 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 08:09:14 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Sat Feb 4 08:09:14 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Sat Feb 4 08:09:18 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0089.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Sat Feb 4 08:09:18 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 08:09:18 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Sat Feb 4 08:09:18 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Sat Feb 4 08:09:18 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 08:09:18 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Sat Feb 4 08:09:18 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Feb 4 08:09:18 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sat Feb 4 08:09:18 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Feb 4 08:09:18 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0089.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 08:09:18 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Feb 4 08:09:18 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 08:09:18 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Feb 4 08:09:19 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 08:09:19 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Feb 4 08:09:19 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Sat Feb 4 08:09:19 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sat Feb 4 08:09:19 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Feb 4 08:09:19 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Sat Feb 4 12:03:08 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0090.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 12:03:08 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Sat Feb 4 12:03:08 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 12:03:08 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Sat Feb 4 12:03:08 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Sat Feb 4 12:03:09 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0090.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Sat Feb 4 12:03:09 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 12:03:09 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Sat Feb 4 12:03:09 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Sat Feb 4 12:03:10 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 12:03:10 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Sat Feb 4 12:03:10 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Feb 4 12:03:10 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sat Feb 4 12:03:10 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Feb 4 12:03:10 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0090.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 12:03:10 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Feb 4 12:03:10 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 12:03:10 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Feb 4 12:03:10 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 12:03:11 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Feb 4 12:03:11 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Sat Feb 4 12:03:11 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sat Feb 4 12:03:11 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Feb 4 12:03:11 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Sat Feb 4 16:01:26 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0091.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 16:01:26 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Sat Feb 4 16:01:26 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 16:01:26 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Sat Feb 4 16:01:26 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Sat Feb 4 16:01:26 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0091.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Sat Feb 4 16:01:26 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 16:01:26 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Sat Feb 4 16:01:26 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Sat Feb 4 16:01:26 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 16:01:26 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Sat Feb 4 16:01:26 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Feb 4 16:01:26 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sat Feb 4 16:01:26 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Feb 4 16:01:26 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0091.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 16:01:26 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Feb 4 16:01:26 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 16:01:26 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Feb 4 16:01:26 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 16:01:26 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Feb 4 16:01:26 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Sat Feb 4 16:01:26 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sat Feb 4 16:01:26 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Feb 4 16:01:26 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Sat Feb 4 20:01:15 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0092.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 20:01:15 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Sat Feb 4 20:01:15 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 20:01:16 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Sat Feb 4 20:01:16 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Sat Feb 4 20:01:16 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0092.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Sat Feb 4 20:01:16 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 20:01:16 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Sat Feb 4 20:01:16 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Sat Feb 4 20:01:16 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 20:01:16 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Sat Feb 4 20:01:16 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Feb 4 20:01:16 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sat Feb 4 20:01:16 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Feb 4 20:01:16 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0092.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 20:01:16 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Feb 4 20:01:16 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 20:01:16 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Feb 4 20:01:16 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 20:01:16 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Feb 4 20:01:16 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Sat Feb 4 20:01:16 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sat Feb 4 20:01:16 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Feb 4 20:01:16 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Sun Feb 5 08:08:18 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0093.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 08:08:18 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Sun Feb 5 08:08:18 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 08:08:19 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Sun Feb 5 08:08:19 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Sun Feb 5 08:08:20 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0093.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Sun Feb 5 08:08:20 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 08:08:20 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Sun Feb 5 08:08:20 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Sun Feb 5 08:08:20 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 08:08:20 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Sun Feb 5 08:08:20 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Feb 5 08:08:20 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sun Feb 5 08:08:20 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Feb 5 08:08:20 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0093.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 08:08:20 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Feb 5 08:08:20 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 08:08:20 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Feb 5 08:08:20 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 08:08:20 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Feb 5 08:08:20 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Sun Feb 5 08:08:20 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sun Feb 5 08:08:20 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Feb 5 08:08:20 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Sun Feb 5 12:03:04 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0094.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 12:03:05 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Sun Feb 5 12:03:05 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 12:03:05 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Sun Feb 5 12:03:05 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Sun Feb 5 12:03:06 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0094.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Sun Feb 5 12:03:06 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 12:03:06 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Sun Feb 5 12:03:06 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Sun Feb 5 12:03:06 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 12:03:06 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Sun Feb 5 12:03:06 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Feb 5 12:03:06 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sun Feb 5 12:03:06 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Feb 5 12:03:07 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0094.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 12:03:07 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Feb 5 12:03:07 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 12:03:07 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Feb 5 12:03:08 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 12:03:08 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Feb 5 12:03:08 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Sun Feb 5 12:03:08 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sun Feb 5 12:03:08 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Feb 5 12:03:08 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Sun Feb 5 16:01:20 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0095.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 16:01:20 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Sun Feb 5 16:01:20 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 16:01:20 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Sun Feb 5 16:01:20 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Sun Feb 5 16:01:20 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0095.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Sun Feb 5 16:01:20 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 16:01:20 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Sun Feb 5 16:01:20 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Sun Feb 5 16:01:20 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 16:01:20 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Sun Feb 5 16:01:20 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Feb 5 16:01:20 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sun Feb 5 16:01:20 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Feb 5 16:01:20 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0095.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 16:01:20 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Feb 5 16:01:20 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 16:01:20 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Feb 5 16:01:20 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 16:01:20 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Feb 5 16:01:20 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Sun Feb 5 16:01:20 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sun Feb 5 16:01:21 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Feb 5 16:01:21 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Sun Feb 5 20:01:13 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0096.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 20:01:14 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Sun Feb 5 20:01:14 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 20:01:14 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Sun Feb 5 20:01:14 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Sun Feb 5 20:01:14 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0096.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Sun Feb 5 20:01:14 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 20:01:14 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Sun Feb 5 20:01:14 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Sun Feb 5 20:01:14 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 20:01:14 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Sun Feb 5 20:01:14 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Feb 5 20:01:14 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sun Feb 5 20:01:14 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Feb 5 20:01:14 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0096.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 20:01:14 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Feb 5 20:01:14 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 20:01:14 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Feb 5 20:01:14 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 20:01:14 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Feb 5 20:01:14 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Sun Feb 5 20:01:14 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sun Feb 5 20:01:15 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Feb 5 20:01:15 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Mon Feb 6 08:16:56 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0097.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 08:16:57 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Mon Feb 6 08:16:57 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 08:16:57 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Mon Feb 6 08:16:57 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Mon Feb 6 08:16:59 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0097.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Mon Feb 6 08:16:59 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 08:16:59 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Mon Feb 6 08:16:59 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Mon Feb 6 08:16:59 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 08:16:59 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Mon Feb 6 08:16:59 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Feb 6 08:16:59 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Mon Feb 6 08:16:59 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Feb 6 08:17:00 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0097.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 08:17:00 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Feb 6 08:17:00 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 08:17:00 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Feb 6 08:17:00 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 08:17:00 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Feb 6 08:17:00 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Mon Feb 6 08:17:00 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Mon Feb 6 08:17:00 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Feb 6 08:17:00 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Mon Feb 6 12:03:12 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0098.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 12:03:12 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Mon Feb 6 12:03:12 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 12:03:12 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Mon Feb 6 12:03:12 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Mon Feb 6 12:03:14 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0098.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Mon Feb 6 12:03:14 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 12:03:14 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Mon Feb 6 12:03:14 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Mon Feb 6 12:03:14 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 12:03:14 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Mon Feb 6 12:03:14 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Feb 6 12:03:14 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Mon Feb 6 12:03:14 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Feb 6 12:03:14 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0098.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 12:03:14 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Feb 6 12:03:14 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 12:03:14 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Feb 6 12:03:14 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 12:03:14 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Feb 6 12:03:14 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Mon Feb 6 12:03:14 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Mon Feb 6 12:03:14 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Feb 6 12:03:14 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Mon Feb 6 16:01:17 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0099.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 16:01:17 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Mon Feb 6 16:01:17 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 16:01:18 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Mon Feb 6 16:01:18 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Mon Feb 6 16:01:18 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0099.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Mon Feb 6 16:01:18 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 16:01:18 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Mon Feb 6 16:01:18 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Mon Feb 6 16:01:18 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 16:01:18 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Mon Feb 6 16:01:18 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Feb 6 16:01:18 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Mon Feb 6 16:01:18 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Feb 6 16:01:18 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0099.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 16:01:18 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Feb 6 16:01:18 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 16:01:18 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Feb 6 16:01:18 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 16:01:18 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Feb 6 16:01:18 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Mon Feb 6 16:01:18 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Mon Feb 6 16:01:18 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Feb 6 16:01:18 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Mon Feb 6 20:01:10 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0100.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 20:01:10 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Mon Feb 6 20:01:10 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 20:01:10 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Mon Feb 6 20:01:10 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Mon Feb 6 20:01:10 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0100.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Mon Feb 6 20:01:10 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 20:01:10 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Mon Feb 6 20:01:10 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Mon Feb 6 20:01:10 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 20:01:10 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Mon Feb 6 20:01:10 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Feb 6 20:01:10 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Mon Feb 6 20:01:10 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Feb 6 20:01:12 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0100.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 20:01:13 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Feb 6 20:01:15 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 20:01:15 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Feb 6 20:01:15 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 20:01:15 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Feb 6 20:01:15 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Mon Feb 6 20:01:15 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Mon Feb 6 20:01:15 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Feb 6 20:01:15 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Tue Feb 7 08:26:43 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0101.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 08:26:43 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Tue Feb 7 08:26:43 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 08:26:43 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Tue Feb 7 08:26:43 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Tue Feb 7 08:26:51 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0101.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Tue Feb 7 08:26:51 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 08:26:51 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Tue Feb 7 08:26:51 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Tue Feb 7 08:26:52 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 08:26:52 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Tue Feb 7 08:26:52 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Feb 7 08:26:52 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Tue Feb 7 08:26:52 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Feb 7 08:26:53 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0101.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 08:26:55 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Feb 7 08:26:55 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 08:26:55 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Feb 7 08:26:56 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 08:26:56 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Feb 7 08:26:56 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Tue Feb 7 08:26:56 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Tue Feb 7 08:26:56 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Feb 7 08:26:56 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Tue Feb 7 12:03:45 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0102.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 12:03:45 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Tue Feb 7 12:03:45 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 12:03:45 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Tue Feb 7 12:03:45 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Tue Feb 7 12:03:46 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0102.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Tue Feb 7 12:03:46 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 12:03:46 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Tue Feb 7 12:03:46 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Tue Feb 7 12:03:46 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 12:03:46 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Tue Feb 7 12:03:46 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Feb 7 12:03:46 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Tue Feb 7 12:03:46 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Feb 7 12:03:46 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0102.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 12:03:46 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Feb 7 12:03:47 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 12:03:47 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Feb 7 12:03:47 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 12:03:47 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Feb 7 12:03:47 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Tue Feb 7 12:03:47 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Tue Feb 7 12:03:47 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Feb 7 12:03:47 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Tue Feb 7 16:01:27 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0103.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 16:01:27 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Tue Feb 7 16:01:27 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 16:01:27 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Tue Feb 7 16:01:27 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Tue Feb 7 16:01:27 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0103.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Tue Feb 7 16:01:27 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 16:01:27 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Tue Feb 7 16:01:27 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Tue Feb 7 16:01:27 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 16:01:27 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Tue Feb 7 16:01:27 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Feb 7 16:01:27 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Tue Feb 7 16:01:27 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Feb 7 16:01:27 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0103.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 16:01:27 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Feb 7 16:01:27 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 16:01:27 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Feb 7 16:01:27 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 16:01:27 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Feb 7 16:01:27 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Tue Feb 7 16:01:27 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Tue Feb 7 16:01:27 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Feb 7 16:01:27 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Tue Feb 7 20:01:19 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0104.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 20:01:19 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Tue Feb 7 20:01:19 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 20:01:19 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Tue Feb 7 20:01:19 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Tue Feb 7 20:01:19 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0104.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Tue Feb 7 20:01:19 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 20:01:19 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Tue Feb 7 20:01:19 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Tue Feb 7 20:01:19 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 20:01:19 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Tue Feb 7 20:01:19 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Feb 7 20:01:19 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Tue Feb 7 20:01:20 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Feb 7 20:01:20 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0104.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 20:01:20 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Feb 7 20:01:20 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 20:01:20 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Feb 7 20:01:20 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 20:01:20 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Feb 7 20:01:20 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Tue Feb 7 20:01:20 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Tue Feb 7 20:01:20 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Feb 7 20:01:20 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Wed Feb 8 08:25:45 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0105.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 08:25:46 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Wed Feb 8 08:25:47 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 08:25:47 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Wed Feb 8 08:25:47 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Wed Feb 8 08:26:00 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0105.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Wed Feb 8 08:26:00 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 08:26:00 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Wed Feb 8 08:26:00 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Wed Feb 8 08:26:00 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 08:26:00 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Wed Feb 8 08:26:00 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Feb 8 08:26:02 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Wed Feb 8 08:26:02 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Feb 8 08:26:02 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0105.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 08:26:02 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Feb 8 08:26:02 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 08:26:02 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Feb 8 08:26:03 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 08:26:03 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Feb 8 08:26:03 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Wed Feb 8 08:26:03 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Wed Feb 8 08:26:03 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Feb 8 08:26:04 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Wed Feb 8 12:03:58 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0106.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 12:03:58 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Wed Feb 8 12:03:58 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 12:03:58 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Wed Feb 8 12:03:58 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Wed Feb 8 12:04:00 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0106.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Wed Feb 8 12:04:00 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 12:04:00 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Wed Feb 8 12:04:00 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Wed Feb 8 12:04:00 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 12:04:00 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Wed Feb 8 12:04:00 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Feb 8 12:04:00 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Wed Feb 8 12:04:00 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Feb 8 12:04:00 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0106.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 12:04:00 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Feb 8 12:04:00 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 12:04:00 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Feb 8 12:04:00 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 12:04:00 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Feb 8 12:04:00 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Wed Feb 8 12:04:00 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Wed Feb 8 12:04:00 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Feb 8 12:04:00 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Wed Feb 8 16:01:31 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0107.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 16:01:32 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Wed Feb 8 16:01:32 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 16:01:32 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Wed Feb 8 16:01:32 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Wed Feb 8 16:01:32 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0107.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Wed Feb 8 16:01:32 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 16:01:32 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Wed Feb 8 16:01:32 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Wed Feb 8 16:01:32 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 16:01:32 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Wed Feb 8 16:01:32 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Feb 8 16:01:32 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Wed Feb 8 16:01:32 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Feb 8 16:01:32 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0107.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 16:01:32 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Feb 8 16:01:32 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 16:01:32 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Feb 8 16:01:32 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 16:01:32 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Feb 8 16:01:32 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Wed Feb 8 16:01:32 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Wed Feb 8 16:01:32 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Feb 8 16:01:32 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Wed Feb 8 20:01:17 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0108.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 20:01:17 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Wed Feb 8 20:01:17 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 20:01:17 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Wed Feb 8 20:01:17 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Wed Feb 8 20:01:17 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0108.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Wed Feb 8 20:01:18 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 20:01:18 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Wed Feb 8 20:01:18 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Wed Feb 8 20:01:18 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 20:01:18 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Wed Feb 8 20:01:18 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Feb 8 20:01:18 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Wed Feb 8 20:01:18 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Feb 8 20:01:18 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0108.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 20:01:18 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Feb 8 20:01:18 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 20:01:18 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Feb 8 20:01:18 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 20:01:18 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Feb 8 20:01:18 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Wed Feb 8 20:01:18 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Wed Feb 8 20:01:18 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Feb 8 20:01:18 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Thu Feb 9 08:10:20 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0109.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 08:10:20 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Thu Feb 9 08:10:20 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 08:10:20 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Thu Feb 9 08:10:20 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Thu Feb 9 08:10:23 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0109.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Thu Feb 9 08:10:23 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 08:10:24 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Thu Feb 9 08:10:24 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Thu Feb 9 08:10:24 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 08:10:24 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Thu Feb 9 08:10:24 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Thu Feb 9 08:10:24 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Thu Feb 9 08:10:24 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Thu Feb 9 08:10:24 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0109.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 08:10:24 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Thu Feb 9 08:10:24 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 08:10:24 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Thu Feb 9 08:10:24 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 08:10:24 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Thu Feb 9 08:10:24 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Thu Feb 9 08:10:24 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Thu Feb 9 08:10:24 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Thu Feb 9 08:10:24 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Thu Feb 9 12:03:41 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0110.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 12:03:41 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Thu Feb 9 12:03:41 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 12:03:41 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Thu Feb 9 12:03:41 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Thu Feb 9 12:03:43 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0110.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Thu Feb 9 12:03:43 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 12:03:43 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Thu Feb 9 12:03:43 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Thu Feb 9 12:03:43 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 12:03:43 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Thu Feb 9 12:03:43 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Thu Feb 9 12:03:43 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Thu Feb 9 12:03:43 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Thu Feb 9 12:03:44 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0110.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 12:03:44 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Thu Feb 9 12:03:44 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 12:03:44 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Thu Feb 9 12:03:44 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 12:03:44 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Thu Feb 9 12:03:44 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Thu Feb 9 12:03:44 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Thu Feb 9 12:03:44 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Thu Feb 9 12:03:44 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Thu Feb 9 16:01:30 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0111.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 16:01:30 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Thu Feb 9 16:01:30 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 16:01:30 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Thu Feb 9 16:01:31 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Thu Feb 9 16:01:31 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0111.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Thu Feb 9 16:01:31 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 16:01:31 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Thu Feb 9 16:01:31 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Thu Feb 9 16:01:31 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 16:01:31 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Thu Feb 9 16:01:31 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Thu Feb 9 16:01:31 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Thu Feb 9 16:01:31 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Thu Feb 9 16:01:31 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0111.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 16:01:31 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Thu Feb 9 16:01:31 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 16:01:31 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Thu Feb 9 16:01:31 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 16:01:31 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Thu Feb 9 16:01:31 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Thu Feb 9 16:01:31 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Thu Feb 9 16:01:31 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Thu Feb 9 16:01:31 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Thu Feb 9 20:01:25 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0112.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 20:01:25 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Thu Feb 9 20:01:25 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 20:01:25 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Thu Feb 9 20:01:25 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Thu Feb 9 20:01:25 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0112.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Thu Feb 9 20:01:25 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 20:01:25 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Thu Feb 9 20:01:25 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Thu Feb 9 20:01:25 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 20:01:25 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Thu Feb 9 20:01:25 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Thu Feb 9 20:01:25 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Thu Feb 9 20:01:25 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Thu Feb 9 20:01:25 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0112.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 20:01:25 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Thu Feb 9 20:01:25 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 20:01:25 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Thu Feb 9 20:01:25 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 20:01:25 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Thu Feb 9 20:01:25 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Thu Feb 9 20:01:25 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Thu Feb 9 20:01:25 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Thu Feb 9 20:01:25 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Fri Feb 10 08:24:37 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0113.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 08:24:41 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Fri Feb 10 08:24:41 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 08:24:41 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Fri Feb 10 08:24:41 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Fri Feb 10 08:25:07 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0113.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Fri Feb 10 08:25:07 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 08:25:07 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Fri Feb 10 08:25:07 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Fri Feb 10 08:25:07 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 08:25:07 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Fri Feb 10 08:25:07 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Feb 10 08:25:07 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Fri Feb 10 08:25:07 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Feb 10 08:25:10 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0113.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 08:25:10 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Feb 10 08:25:10 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 08:25:12 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Feb 10 08:25:12 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 08:25:12 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Feb 10 08:25:12 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Fri Feb 10 08:25:12 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Fri Feb 10 08:25:12 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Feb 10 08:25:13 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Fri Feb 10 12:04:02 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0114.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 12:04:03 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Fri Feb 10 12:04:03 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 12:04:03 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Fri Feb 10 12:04:03 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Fri Feb 10 12:04:05 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0114.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Fri Feb 10 12:04:05 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 12:04:05 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Fri Feb 10 12:04:05 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Fri Feb 10 12:04:05 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 12:04:05 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Fri Feb 10 12:04:05 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Feb 10 12:04:05 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Fri Feb 10 12:04:05 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Feb 10 12:04:05 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0114.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 12:04:05 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Feb 10 12:04:05 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 12:04:05 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Feb 10 12:04:05 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 12:04:05 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Feb 10 12:04:05 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Fri Feb 10 12:04:05 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Fri Feb 10 12:04:05 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Feb 10 12:04:05 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Fri Feb 10 16:01:23 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0115.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 16:01:23 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Fri Feb 10 16:01:23 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 16:01:23 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Fri Feb 10 16:01:23 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Fri Feb 10 16:01:23 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0115.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Fri Feb 10 16:01:23 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 16:01:24 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Fri Feb 10 16:01:24 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Fri Feb 10 16:01:24 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 16:01:24 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Fri Feb 10 16:01:24 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Feb 10 16:01:24 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Fri Feb 10 16:01:24 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Feb 10 16:01:24 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0115.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 16:01:24 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Feb 10 16:01:24 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 16:01:24 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Feb 10 16:01:24 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 16:01:24 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Feb 10 16:01:24 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Fri Feb 10 16:01:24 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Fri Feb 10 16:01:24 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Feb 10 16:01:24 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Fri Feb 10 20:01:23 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0116.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 20:01:23 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Fri Feb 10 20:01:23 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 20:01:23 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Fri Feb 10 20:01:23 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Fri Feb 10 20:01:23 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0116.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Fri Feb 10 20:01:23 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 20:01:23 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Fri Feb 10 20:01:23 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Fri Feb 10 20:01:23 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 20:01:23 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Fri Feb 10 20:01:23 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Feb 10 20:01:23 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Fri Feb 10 20:01:23 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Feb 10 20:01:23 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0116.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 20:01:23 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Feb 10 20:01:23 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 20:01:23 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Feb 10 20:01:23 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 20:01:23 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Feb 10 20:01:23 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Fri Feb 10 20:01:24 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Fri Feb 10 20:01:24 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Feb 10 20:01:24 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Sat Feb 11 08:13:48 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0117.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 08:13:48 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Sat Feb 11 08:13:48 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 08:13:49 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Sat Feb 11 08:13:49 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Sat Feb 11 08:13:52 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0117.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Sat Feb 11 08:13:53 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 08:13:53 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Sat Feb 11 08:13:53 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Sat Feb 11 08:13:53 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 08:13:53 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Sat Feb 11 08:13:53 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Feb 11 08:13:53 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sat Feb 11 08:13:53 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Feb 11 08:13:54 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0117.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 08:13:54 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Feb 11 08:13:54 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 08:13:54 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Feb 11 08:13:54 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 08:13:54 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Feb 11 08:13:54 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Sat Feb 11 08:13:54 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sat Feb 11 08:13:54 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Feb 11 08:13:55 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Sat Feb 11 12:03:07 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0118.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 12:03:07 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Sat Feb 11 12:03:07 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 12:03:07 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Sat Feb 11 12:03:07 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Sat Feb 11 12:03:09 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0118.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Sat Feb 11 12:03:09 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 12:03:09 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Sat Feb 11 12:03:09 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Sat Feb 11 12:03:09 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 12:03:09 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Sat Feb 11 12:03:09 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Feb 11 12:03:09 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sat Feb 11 12:03:09 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Feb 11 12:03:09 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0118.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 12:03:09 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Feb 11 12:03:09 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 12:03:09 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Feb 11 12:03:09 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 12:03:09 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Feb 11 12:03:09 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Sat Feb 11 12:03:09 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sat Feb 11 12:03:09 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Feb 11 12:03:10 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Sat Feb 11 16:01:17 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0119.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 16:01:17 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Sat Feb 11 16:01:17 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 16:01:17 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Sat Feb 11 16:01:17 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Sat Feb 11 16:01:17 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0119.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Sat Feb 11 16:01:17 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 16:01:17 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Sat Feb 11 16:01:17 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Sat Feb 11 16:01:17 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 16:01:17 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Sat Feb 11 16:01:17 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Feb 11 16:01:17 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sat Feb 11 16:01:17 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Feb 11 16:01:17 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0119.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 16:01:17 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Feb 11 16:01:17 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 16:01:17 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Feb 11 16:01:17 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 16:01:17 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Feb 11 16:01:17 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Sat Feb 11 16:01:17 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sat Feb 11 16:01:17 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Feb 11 16:01:17 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Sat Feb 11 20:01:10 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0120.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 20:01:10 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Sat Feb 11 20:01:10 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 20:01:10 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Sat Feb 11 20:01:10 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Sat Feb 11 20:01:10 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0120.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Sat Feb 11 20:01:10 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 20:01:10 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Sat Feb 11 20:01:10 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Sat Feb 11 20:01:10 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 20:01:10 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Sat Feb 11 20:01:10 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Feb 11 20:01:10 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sat Feb 11 20:01:10 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Feb 11 20:01:10 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0120.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 20:01:10 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Feb 11 20:01:10 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 20:01:10 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sat Feb 11 20:01:10 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 20:01:10 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Feb 11 20:01:10 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Sat Feb 11 20:01:10 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sat Feb 11 20:01:10 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sat Feb 11 20:01:10 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Sun Feb 12 08:10:29 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0121.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 08:10:30 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Sun Feb 12 08:10:30 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 08:10:30 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Sun Feb 12 08:10:31 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Sun Feb 12 08:10:34 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0121.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Sun Feb 12 08:10:34 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 08:10:34 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Sun Feb 12 08:10:34 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Sun Feb 12 08:10:34 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 08:10:34 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Sun Feb 12 08:10:34 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Feb 12 08:10:34 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sun Feb 12 08:10:35 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Feb 12 08:10:35 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0121.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 08:10:35 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Feb 12 08:10:35 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 08:10:35 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Feb 12 08:10:35 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 08:10:35 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Feb 12 08:10:35 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Sun Feb 12 08:10:35 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sun Feb 12 08:10:35 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Feb 12 08:10:36 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Sun Feb 12 12:03:12 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0122.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 12:03:12 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Sun Feb 12 12:03:12 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 12:03:12 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Sun Feb 12 12:03:12 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Sun Feb 12 12:03:14 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0122.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Sun Feb 12 12:03:14 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 12:03:14 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Sun Feb 12 12:03:14 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Sun Feb 12 12:03:14 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 12:03:14 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Sun Feb 12 12:03:14 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Feb 12 12:03:14 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sun Feb 12 12:03:14 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Feb 12 12:03:14 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0122.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 12:03:14 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Feb 12 12:03:14 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 12:03:14 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Feb 12 12:03:14 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 12:03:14 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Feb 12 12:03:14 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Sun Feb 12 12:03:14 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sun Feb 12 12:03:14 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Feb 12 12:03:14 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Sun Feb 12 16:01:23 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0123.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 16:01:23 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Sun Feb 12 16:01:23 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 16:01:23 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Sun Feb 12 16:01:23 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Sun Feb 12 16:01:23 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0123.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Sun Feb 12 16:01:23 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 16:01:23 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Sun Feb 12 16:01:23 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Sun Feb 12 16:01:23 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 16:01:23 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Sun Feb 12 16:01:23 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Feb 12 16:01:23 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sun Feb 12 16:01:23 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Feb 12 16:01:23 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0123.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 16:01:23 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Feb 12 16:01:23 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 16:01:23 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Feb 12 16:01:23 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 16:01:24 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Feb 12 16:01:24 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Sun Feb 12 16:01:24 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sun Feb 12 16:01:24 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Feb 12 16:01:24 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Sun Feb 12 20:01:13 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0124.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 20:01:13 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Sun Feb 12 20:01:13 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 20:01:13 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Sun Feb 12 20:01:13 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Sun Feb 12 20:01:13 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0124.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Sun Feb 12 20:01:13 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 20:01:13 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Sun Feb 12 20:01:13 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Sun Feb 12 20:01:13 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 20:01:13 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Sun Feb 12 20:01:13 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Feb 12 20:01:14 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sun Feb 12 20:01:14 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Feb 12 20:01:14 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0124.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 20:01:14 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Feb 12 20:01:14 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 20:01:14 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Sun Feb 12 20:01:14 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 20:01:14 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Feb 12 20:01:14 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Sun Feb 12 20:01:14 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Sun Feb 12 20:01:14 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Sun Feb 12 20:01:14 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Mon Feb 13 08:18:58 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0125.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 08:18:58 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Mon Feb 13 08:18:58 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 08:18:58 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Mon Feb 13 08:18:58 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Mon Feb 13 08:19:01 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0125.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Mon Feb 13 08:19:01 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 08:19:01 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Mon Feb 13 08:19:01 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Mon Feb 13 08:19:01 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 08:19:02 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Mon Feb 13 08:19:02 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Feb 13 08:19:02 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Mon Feb 13 08:19:02 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Feb 13 08:19:02 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0125.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 08:19:02 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Feb 13 08:19:02 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 08:19:02 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Feb 13 08:19:02 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 08:19:03 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Feb 13 08:19:03 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Mon Feb 13 08:19:04 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Mon Feb 13 08:19:05 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Feb 13 08:19:05 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Mon Feb 13 12:03:33 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0126.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 12:03:33 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Mon Feb 13 12:03:33 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 12:03:33 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Mon Feb 13 12:03:33 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Mon Feb 13 12:03:35 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0126.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Mon Feb 13 12:03:35 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 12:03:35 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Mon Feb 13 12:03:36 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Mon Feb 13 12:03:36 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 12:03:36 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Mon Feb 13 12:03:36 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Feb 13 12:03:36 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Mon Feb 13 12:03:36 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Feb 13 12:03:36 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0126.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 12:03:36 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Feb 13 12:03:36 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 12:03:36 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Feb 13 12:03:36 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 12:03:36 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Feb 13 12:03:36 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Mon Feb 13 12:03:36 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Mon Feb 13 12:03:36 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Feb 13 12:03:36 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Mon Feb 13 16:01:37 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0127.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 16:01:37 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Mon Feb 13 16:01:37 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 16:01:37 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Mon Feb 13 16:01:37 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Mon Feb 13 16:01:37 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0127.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Mon Feb 13 16:01:37 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 16:01:37 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Mon Feb 13 16:01:37 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Mon Feb 13 16:01:37 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 16:01:37 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Mon Feb 13 16:01:37 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Feb 13 16:01:37 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Mon Feb 13 16:01:37 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Feb 13 16:01:37 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0127.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 16:01:37 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Feb 13 16:01:37 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 16:01:37 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Feb 13 16:01:37 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 16:01:37 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Feb 13 16:01:37 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Mon Feb 13 16:01:37 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Mon Feb 13 16:01:37 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Feb 13 16:01:37 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Mon Feb 13 20:01:22 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0128.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 20:01:22 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Mon Feb 13 20:01:22 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 20:01:22 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Mon Feb 13 20:01:22 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Mon Feb 13 20:01:22 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0128.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Mon Feb 13 20:01:22 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 20:01:22 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Mon Feb 13 20:01:22 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Mon Feb 13 20:01:22 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 20:01:22 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Mon Feb 13 20:01:22 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Feb 13 20:01:22 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Mon Feb 13 20:01:22 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Feb 13 20:01:22 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0128.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 20:01:22 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Feb 13 20:01:22 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 20:01:22 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Mon Feb 13 20:01:22 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 20:01:22 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Feb 13 20:01:22 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Mon Feb 13 20:01:22 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Mon Feb 13 20:01:22 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Mon Feb 13 20:01:22 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Tue Feb 14 08:21:15 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0129.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 08:21:16 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Tue Feb 14 08:21:16 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 08:21:16 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Tue Feb 14 08:21:17 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Tue Feb 14 08:21:21 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0129.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Tue Feb 14 08:21:23 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 08:21:23 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Tue Feb 14 08:21:23 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Tue Feb 14 08:21:23 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 08:21:23 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Tue Feb 14 08:21:23 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Feb 14 08:21:24 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Tue Feb 14 08:21:24 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Feb 14 08:21:24 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0129.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 08:21:24 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Feb 14 08:21:24 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 08:21:24 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Feb 14 08:21:25 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 08:21:25 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Feb 14 08:21:25 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Tue Feb 14 08:21:26 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Tue Feb 14 08:21:26 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Feb 14 08:21:26 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Tue Feb 14 12:03:50 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0130.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 12:03:51 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Tue Feb 14 12:03:51 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 12:03:51 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Tue Feb 14 12:03:51 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Tue Feb 14 12:03:52 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0130.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Tue Feb 14 12:03:52 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 12:03:52 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Tue Feb 14 12:03:52 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Tue Feb 14 12:03:52 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 12:03:52 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Tue Feb 14 12:03:52 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Feb 14 12:03:52 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Tue Feb 14 12:03:52 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Feb 14 12:03:52 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0130.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 12:03:53 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Feb 14 12:03:53 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 12:03:53 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Feb 14 12:03:53 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 12:03:53 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Feb 14 12:03:53 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Tue Feb 14 12:03:53 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Tue Feb 14 12:03:53 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Feb 14 12:03:53 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Tue Feb 14 16:01:55 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0131.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 16:01:56 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Tue Feb 14 16:01:56 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 16:01:56 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Tue Feb 14 16:01:56 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Tue Feb 14 16:01:56 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0131.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Tue Feb 14 16:01:56 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 16:01:56 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Tue Feb 14 16:01:56 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Tue Feb 14 16:01:56 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 16:01:56 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Tue Feb 14 16:01:56 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Feb 14 16:01:56 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Tue Feb 14 16:01:56 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Feb 14 16:01:56 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0131.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 16:01:56 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Feb 14 16:01:56 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 16:01:56 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Feb 14 16:01:56 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 16:01:56 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Feb 14 16:01:56 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Tue Feb 14 16:01:56 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Tue Feb 14 16:01:56 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Feb 14 16:01:56 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Tue Feb 14 20:01:23 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0132.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 20:01:23 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Tue Feb 14 20:01:23 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 20:01:23 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Tue Feb 14 20:01:23 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Tue Feb 14 20:01:23 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0132.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Tue Feb 14 20:01:23 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 20:01:23 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Tue Feb 14 20:01:23 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Tue Feb 14 20:01:23 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 20:01:23 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Tue Feb 14 20:01:23 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Feb 14 20:01:23 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Tue Feb 14 20:01:23 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Feb 14 20:01:24 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0132.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 20:01:24 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Feb 14 20:01:24 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 20:01:24 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Tue Feb 14 20:01:24 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 20:01:24 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Feb 14 20:01:24 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Tue Feb 14 20:01:24 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Tue Feb 14 20:01:24 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Tue Feb 14 20:01:24 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Wed Feb 15 08:32:31 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0133.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 08:32:32 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Wed Feb 15 08:32:35 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 08:32:35 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Wed Feb 15 08:32:35 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Wed Feb 15 08:32:53 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0133.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Wed Feb 15 08:32:53 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 08:32:53 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Wed Feb 15 08:32:53 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Wed Feb 15 08:32:53 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 08:32:53 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Wed Feb 15 08:32:54 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Feb 15 08:32:54 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Wed Feb 15 08:32:54 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Feb 15 08:32:55 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0133.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 08:32:55 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Feb 15 08:32:55 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 08:32:55 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Feb 15 08:32:55 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 08:32:55 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Feb 15 08:32:55 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Wed Feb 15 08:32:55 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Wed Feb 15 08:32:55 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Feb 15 08:32:55 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Wed Feb 15 12:06:05 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0134.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 12:06:05 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Wed Feb 15 12:06:05 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 12:06:05 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Wed Feb 15 12:06:05 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Wed Feb 15 12:06:07 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0134.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Wed Feb 15 12:06:07 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 12:06:07 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Wed Feb 15 12:06:07 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Wed Feb 15 12:06:07 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 12:06:07 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Wed Feb 15 12:06:07 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Feb 15 12:06:07 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Wed Feb 15 12:06:08 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Feb 15 12:06:08 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0134.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 12:06:08 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Feb 15 12:06:08 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 12:06:08 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Feb 15 12:06:08 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 12:06:08 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Feb 15 12:06:08 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Wed Feb 15 12:06:08 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Wed Feb 15 12:06:08 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Feb 15 12:06:08 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Wed Feb 15 16:01:48 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0135.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 16:01:49 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Wed Feb 15 16:01:49 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 16:01:49 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Wed Feb 15 16:01:49 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Wed Feb 15 16:01:49 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0135.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Wed Feb 15 16:01:49 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 16:01:49 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Wed Feb 15 16:01:49 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Wed Feb 15 16:01:49 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 16:01:49 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Wed Feb 15 16:01:49 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Feb 15 16:01:49 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Wed Feb 15 16:01:49 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Feb 15 16:01:49 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0135.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 16:01:49 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Feb 15 16:01:49 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 16:01:49 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Feb 15 16:01:49 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 16:01:49 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Feb 15 16:01:49 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Wed Feb 15 16:01:49 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Wed Feb 15 16:01:49 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Feb 15 16:01:49 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Wed Feb 15 19:28:25 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0136.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 19:28:25 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Wed Feb 15 19:28:25 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 19:28:25 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Wed Feb 15 19:28:25 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Wed Feb 15 19:28:25 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0136.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Wed Feb 15 19:28:25 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 19:28:25 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Wed Feb 15 19:28:25 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Wed Feb 15 19:28:25 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 19:28:27 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Wed Feb 15 19:28:27 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Feb 15 19:28:27 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Wed Feb 15 19:28:27 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Feb 15 19:28:27 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0136.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 19:28:27 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Feb 15 19:28:28 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 19:28:28 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Feb 15 19:28:28 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 19:28:28 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Feb 15 19:28:28 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Wed Feb 15 19:28:28 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Wed Feb 15 19:28:28 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Feb 15 19:28:28 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Wed Feb 15 20:15:16 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0137.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 20:15:16 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Wed Feb 15 20:15:16 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 20:15:16 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Wed Feb 15 20:15:16 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Wed Feb 15 20:15:19 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0137.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Wed Feb 15 20:15:19 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 20:15:19 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Wed Feb 15 20:15:19 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Wed Feb 15 20:15:19 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 20:15:20 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Wed Feb 15 20:15:20 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Feb 15 20:15:20 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Wed Feb 15 20:15:20 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Feb 15 20:15:20 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0137.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 20:15:20 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Feb 15 20:15:20 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 20:15:20 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Wed Feb 15 20:15:20 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 20:15:20 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Feb 15 20:15:20 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Wed Feb 15 20:15:20 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Wed Feb 15 20:15:20 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Wed Feb 15 20:15:20 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Thu Feb 16 08:49:40 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0138.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 16 08:49:41 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Thu Feb 16 08:49:41 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 16 08:49:41 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Thu Feb 16 08:49:41 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Thu Feb 16 08:49:47 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0138.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Thu Feb 16 08:49:47 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 16 08:49:48 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Thu Feb 16 08:49:48 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Thu Feb 16 08:49:50 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 16 08:49:51 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Thu Feb 16 08:49:51 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Thu Feb 16 08:49:51 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Thu Feb 16 08:49:51 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Thu Feb 16 08:49:53 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0138.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 16 08:49:53 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Thu Feb 16 08:49:53 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 16 08:49:53 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Thu Feb 16 08:49:54 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 16 08:49:54 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Thu Feb 16 08:49:54 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Thu Feb 16 08:49:54 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Thu Feb 16 08:49:55 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Thu Feb 16 08:49:55 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 bgibson at us.ibm.com Tue Mar 1 21:00:03 2005 From: bgibson at us.ibm.com (Bob Gibson) Date: Fri Mar 31 16:34:08 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? Message-ID: >... > Interesting, so Derby (Cloudscape) and DB2 talk the same > wire protocol ? > > Perhaps you could ask the developers whether the missing > rowcount information is per design or simply a bug in the > ODBC driver ?! > > Such information is usually rather important to have, esp. > in cases where you want to page through large data sets. > > Thanks, > -- > Marc-Andre Lemburg > eGenix.com ---------------------------------------------------------------------- Marc-Andre: What ODBC calls does mxODBC used to implement the fetchall()? When I look at the ODBC documentation at the Microsmurf site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp The closest routine I can find is the SQLExtendedFetch Function. Is this what you use? Bob-------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050301/0e9d3e5d/attachment-0139.htm From mal at egenix.com Wed Mar 2 10:08:03 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Mar 31 16:34:09 2006 Subject: [egenix-users] Re: mxODBC - How do I "set schema"? In-Reply-To: References: Message-ID: <42258273.7060204@egenix.com> Bob Gibson wrote: > > > >>... >>Interesting, so Derby (Cloudscape) and DB2 talk the same >>wire protocol ? >> >>Perhaps you could ask the developers whether the missing >>rowcount information is per design or simply a bug in the >>ODBC driver ?! >> >>Such information is usually rather important to have, esp. >>in cases where you want to page through large data sets. >> >>Thanks, >>-- >>Marc-Andre Lemburg >>eGenix.com > > ---------------------------------------------------------------------- > > Marc-Andre: > > What ODBC calls does mxODBC used to implement the fetchall()? When > I look at the ODBC documentation at the Microsmurf site: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_api_reference.asp > > The closest routine I can find is the SQLExtendedFetch Function. Is > this what you use? The 2.0.x version uses SQLFetch(). The 2.1.x which is used in the mxODBC Zope DA uses SQLFecthScroll() if available and falls back to plain SQLFetch() if that API is not supported by the ODBC driver. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 02 2005) >>> 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 steve at holdenweb.com Thu Mar 3 00:36:48 2005 From: steve at holdenweb.com (Steve Holden) Date: Fri Mar 31 16:34:09 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: References: Message-ID: <4226A270.3@holdenweb.com> Joe wrote: > Python 2.4 > Windows XP SP2 > MS Access 2000 > mx.ODBC 2.0.7 > > Problem data truncation occuring (here's the actual error message): > > mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access Driver] > String data, right truncated on column number 3 (Expr1002)', 3326) > > I believe that have found a bug in mx.ODBC not properly assigning the > correct data type to a column. > > Here is a sample script that demonstrates the problem and why I think it is > being handled incorrectly: > > # NOTE memo1 and memo2 are memo fields in the test_table > > import mx.ODBC.Windows > > dbs = mx.ODBC.Windows.connect('database', '', '') > > sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where > record_id = 1" > > c = dbs.cursor() > > c.execute(sql) > > print > print 'mxODBC SQL DataTypes:' > print > > for i in mx.ODBC.Windows.sqltype: > print i, mx.ODBC.Windows.sqltype[i] > > print > print 'Column DataTypes:' > print > > for i in range(len(c.description)): > print c.description[i][1] > > c.close() > dbs.close() > > When you run this script it produces the following output: > > mxODBC SQL DataTypes: > > 1 CHAR > 2 NUMERIC > 3 DECIMAL > 4 INTEGER > 5 SMALLINT > 6 FLOAT > 7 REAL > 8 DOUBLE > 9 DATE > 10 TIME > 11 TIMESTAMP > 12 VARCHAR > 91 TYPE_DATE > 92 TYPE_TIME > 93 TYPE_TIMESTAMP > -1 LONGVARCHAR > -10 WCHAR_LONGVARCHAR > -9 WCHAR_VARCHAR > -8 WCHAR > -7 BIT > -6 TINYINT > -5 BIGINT > -4 LONGVARBINARY > -3 VARBINARY > -2 BINARY > > Column DataTypes: > > -1 > -1 > 12 > > From the output you can see that memo1 and memo2 are both determined to be > of type longvarchar (-1) but when the columns are concatenated together the > resulting column is given a type of varchar (12). Obviously this is why the > data truncation is occurring. > > Is this a known problem? > > I can work around the problem using a converter function: > > def converter(position, sqltype, sqllen): > print 'in :', position, sqltype, sqllen > if position == 2: > sqltype = -1 > sqllen = 1073741823 > print 'out:', position, sqltype, sqllen > return sqltype, sqllen > > and then using: > > c.setconverter(converter) > > but shouldn't mx.ODBC have properly assigned the correct sqltype and sqllen > for the concatenated memo columns in the first place? > This is a very nice piece of deduction, and I am copying this message to you and to the egenix-users list, since that's generally a reliable way to get Marc-Andre's attention. I'm not convinced that it demonstrates an mxODBC bug, since I don't believe that the ampersand is actioned by the drivers, but I'm not the best one to be authoritative about this. others-who-read-this-reply-will-ly y'rs - steve -- Meet the Python developers and your c.l.py favorites March 23-25 Come to PyCon DC 2005 http://www.pycon.org/ Steve Holden http://www.holdenweb.com/ From mal at egenix.com Thu Mar 3 11:11:12 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Mar 31 16:34:09 2006 Subject: [egenix-users] Re: mx.ODBC 2.0.7 bug? In-Reply-To: <4226A270.3@holdenweb.com> References: <4226A270.3@holdenweb.com> Message-ID: <4226E2C0.4090507@egenix.com> Thanks for forwarding the message, Steve. Steve Holden wrote: > Joe wrote: > >> Python 2.4 >> Windows XP SP2 >> MS Access 2000 >> mx.ODBC 2.0.7 >> >> Problem data truncation occuring (here's the actual error message): >> >> mxODBC.Warning: ('01004', 5, '[Microsoft][ODBC Microsoft Access >> Driver] String data, right truncated on column number 3 (Expr1002)', >> 3326) >> >> I believe that have found a bug in mx.ODBC not properly assigning the >> correct data type to a column. >> >> Here is a sample script that demonstrates the problem and why I think >> it is being handled incorrectly: >> >> # NOTE memo1 and memo2 are memo fields in the test_table >> >> import mx.ODBC.Windows >> >> dbs = mx.ODBC.Windows.connect('database', '', '') >> >> sql = "select memo1, memo2, memo1 & ' ' & memo2 from test_table where >> record_id = 1" >> >> c = dbs.cursor() >> >> c.execute(sql) >> >> print >> print 'mxODBC SQL DataTypes:' >> print >> >> for i in mx.ODBC.Windows.sqltype: >> print i, mx.ODBC.Windows.sqltype[i] >> >> print >> print 'Column DataTypes:' >> print >> >> for i in range(len(c.description)): >> print c.description[i][1] >> >> c.close() >> dbs.close() >> >> When you run this script it produces the following output: >> >> mxODBC SQL DataTypes: >> >> 1 CHAR >> 2 NUMERIC >> 3 DECIMAL >> 4 INTEGER >> 5 SMALLINT >> 6 FLOAT >> 7 REAL >> 8 DOUBLE >> 9 DATE >> 10 TIME >> 11 TIMESTAMP >> 12 VARCHAR >> 91 TYPE_DATE >> 92 TYPE_TIME >> 93 TYPE_TIMESTAMP >> -1 LONGVARCHAR >> -10 WCHAR_LONGVARCHAR >> -9 WCHAR_VARCHAR >> -8 WCHAR >> -7 BIT >> -6 TINYINT >> -5 BIGINT >> -4 LONGVARBINARY >> -3 VARBINARY >> -2 BINARY >> >> Column DataTypes: >> >> -1 >> -1 >> 12 >> >> From the output you can see that memo1 and memo2 are both determined >> to be of type longvarchar (-1) but when the columns are concatenated >> together the resulting column is given a type of varchar (12). >> Obviously this is why the data truncation is occurring. >> >> Is this a known problem? No, but then the MS Access ODBC drivers are always full of surprises :-) (things have gotten a lot better recently, though). >> I can work around the problem using a converter function: >> >> def converter(position, sqltype, sqllen): >> print 'in :', position, sqltype, sqllen >> if position == 2: >> sqltype = -1 >> sqllen = 1073741823 >> print 'out:', position, sqltype, sqllen >> return sqltype, sqllen >> >> and then using: >> >> c.setconverter(converter) >> >> but shouldn't mx.ODBC have properly assigned the correct sqltype and >> sqllen for the concatenated memo columns in the first place? mxODBC gets the select column information from the ODBC driver and then fetches the data rows based on that information. In the above case, the Access ODBC driver tells mxODBC that the third column is of type VARCHAR and passes it some length information that obviously is wrong. The only way to fix this is using a converter like you did. BTW, do you have more info on the length of the memo field contents and the value that Access passes back as sqllen for the third column ? It is possible that this is some off-by-one bug in the driver. We could work around that by creating a larger buffer to hold the data. > This is a very nice piece of deduction, and I am copying this message to > you and to the egenix-users list, since that's generally a reliable way > to get Marc-Andre's attention. Indeed :-) (don't read c.l.p that often these days) > I'm not convinced that it demonstrates an mxODBC bug, since I don't > believe that the ampersand is actioned by the drivers, but I'm not the > best one to be authoritative about this. > > others-who-read-this-reply-will-ly y'rs - steve -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 03 2005) >>> 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 support at egenix.com Wed Mar 9 14:24:57 2005 From: support at egenix.com (Charlie Clark) Date: Fri Mar 31 16:34:09 2006 Subject: [egenix-users] Re: [egenix-sales] mxODBC Zope DA Zope Evaluation License(s) In-Reply-To: <422EF1EB.4020600@citromail.hu> References: <20050309084311.2502E1C2CB@mail.egenix.com> <422EF1EB.4020600@citromail.hu> Message-ID: <20050309142457.3669.2@Zeta.1110371118.fake> On 2005-03-09 at 13:54:03 [+0100], fowlertrainer@citromail.hu wrote: > Hi ! > > It is an interesting thing. > > I have a machine (Windows XP) with preinstalled python, and zope. In > this machine the mxodbc installation is working good, the Zope can start > itself. > > But I have a new machine without python (Windows 2000). > I install newest version of Zope (2.7.4 I think). > > I don't use "Program Files" (space char. problems): I use c:\Zope, and > c:\Zope\Instance dirs. > > I copy the mx da files and dirs to c:\Zope\lib\Python. > I copy the test licence files to c:\Zope\lib\Python\mx\ODBC. > > When I try to start Zope manually, I get error like in attachment. > > Why ? > > It is need to I install mxODBC package ? Or what ? > > I cannot understand it, because in XP that is working. In W2K Zope is > working without mxODBCDA. > What is the solution ? Please help me ! > > Thanx for it: > ft Hi L?szl?, Zope2.7 by default will not start if there is a problem loading a product. You can adjust settings for this in Instance/etc/zope.conf The reason mxODBCZopeDA cannot start is because the licence file and library is in the wrong path. The actual Python path is actually Zope/bin and not Zope/lib/Python. Move the mx folder to the lib/site-packages folder and restart. Good luck! Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 c.thornton at fi.com Thu Mar 10 19:06:09 2005 From: c.thornton at fi.com (Chris Thornton) Date: Fri Mar 31 16:34:11 2006 Subject: [egenix-users] Sales Force Automation Application Message-ID: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> - When connecting via mxODBCZope and connection fails the connector does not auto-recover. - When connection to a stored procedure that returns a datetime in the wrong format it freezes the ZOPE service. Please send us any information you might have about the two issues. Christopher Thornton Web Developer Fisher Investments, Inc. PLEASE READ THIS WARNING: Investment in securities involves the risk of loss. Past performance is no guarantee of future returns. Other methods may produce different results, and the results for different periods may vary depending on market conditions and the composition of the portfolio. Warning: Do not send time-sensitive, action-oriented messages, such as transaction requests, via e-mail as it is our policy not to accept such items electronically. All e-mail sent to or from this address will be received or otherwise recorded by the Fisher Investments corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050310/85ec629c/attachment-0139.htm From charlie at egenix.com Fri Mar 11 10:18:01 2005 From: charlie at egenix.com (Charlie Clark) Date: Fri Mar 31 16:34:11 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> Message-ID: <20050311101801.818.1@Zeta.1110532364.fake> Dear Chris, without more information we can't say a lot about this but neither problem is likely to be related to mxODBC. Connection problems are usually related to ODBC manager or network issues. Can you please provide more information about your set up and also the stored procedure. Why does the stored procedure return a datetime in the wrong format? Regards Charlie On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > - When connecting via mxODBCZope and connection fails the > connector does not auto-recover. > > - When connection to a stored procedure that returns a datetime > in the wrong format it freezes the ZOPE service. > > > > Please send us any information you might have about the two issues. > > > > Christopher Thornton > > Web Developer > > Fisher Investments, Inc. From mal at egenix.com Fri Mar 11 17:20:51 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Mar 31 16:34:11 2006 Subject: [egenix-users] Sales Force Automation Application In-Reply-To: <20050311101801.818.1@Zeta.1110532364.fake> References: <3D9D8F616F723040908E63DCEC90F3780139A3F5@whiteshark.fi.com> <20050311101801.818.1@Zeta.1110532364.fake> Message-ID: <4231C563.3070105@egenix.com> Charlie Clark wrote: > Dear Chris, > > without more information we can't say a lot about this but neither problem > is likely to be related to mxODBC. Connection problems are usually related > to ODBC manager or network issues. > > Can you please provide more information about your set up and also the > stored procedure. Why does the stored procedure return a datetime in the > wrong format? Please always provide at least these bits of information when you run into a problem: * Python version * Zope version * mxODBC Zope DA version * Database and version * ODBC driver and version (most of this information is available on the mxODBC Zope DA connection status page) * Most important: Zope tracebacks and log file excerpts As Charlie already said, without such information we are unable to respond to requests like yours. > Regards > > Charlie > > On 2005-03-11 at 04:06:09 [+0100], Chris Thornton wrote: > >>- When connecting via mxODBCZope and connection fails the >>connector does not auto-recover. >> >>- When connection to a stored procedure that returns a datetime >>in the wrong format it freezes the ZOPE service. >> >> >> >>Please send us any information you might have about the two issues. >> >> >> >>Christopher Thornton >> >>Web Developer >> >>Fisher Investments, Inc. > > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 11 2005) >>> 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 support at egenix.com Wed Mar 23 09:59:39 2005 From: support at egenix.com (Charlie Clark) Date: Fri Mar 31 16:34:11 2006 Subject: [egenix-users] RE: [egenix-sales] Evaluation In-Reply-To: References: Message-ID: <20050323095939.1182.5@Zeta.1111567839.fake> On 2005-03-22 at 21:03:19 [+0100], Scott Robinson wrote: > I changed the Maximum rows to retrieve to'9999' and the Maximum results to > cache to '9999' But I still get the error, here is the tracefile. Hope this > is what your looking for. > > Time 2005/03/22 15:59:59.373 US/Eastern > User Name (User Id) admin (admin) > Request URL http://10.2.2.23/waterloo/it/sql_select_all_eventlog/manage_test > > Exception Type KeyError > Exception Value 'query' > > Traceback (innermost last): > > Module ZPublisher.Publish, line 101, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 39, in call_object > Module Shared.DC.ZRDB.DA, line 337, in manage_test > Module DocumentTemplate.DT_String, line 474, in __call__ > Module DocumentTemplate.DT_In, line 602, in renderwb > Module DocumentTemplate.DT_Var, line 219, in render > KeyError: 'query' > > Display traceback as text Dear Scott, this is an error in your PageTemplate and almost definitely unrelated to the mxODBCZopeDA. You are trying to access an object called "query" which does not exist in the local namespace. Might be able to say more if you send the template. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> 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 john.ertl at fnmoc.navy.mil Wed Mar 23 13:02:51 2005 From: john.ertl at fnmoc.navy.mil (Ertl, John) Date: Fri Mar 31 16:34:11 2006 Subject: [egenix-users] getting a gcc error durin install Message-ID: All, I am trying to install egenix-mx-commercial-2.0.7 from source and I am getting the following error. I am not much of a systems person but Python 2.4 and all of the modules have installed with out this problem so I am sure what the issue might be. I am running on RedHat ES 3.0 . I could not find this issue in the archive or on goggle. I was able to install the BASE just fine. Any ideas? Thanks ....skipping.... mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function `SQLAllocEnv' mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this function) mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this function) error: command '/usr/bin/gcc' failed with exit status 1 [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) John C. Ertl Fleet Numerical Meteorology & Oceanography Center 7 Grace Hopper Ave Monterey, CA 93943 phone: (831) 656-5704 fax: (831) 656-4363 From mal at egenix.com Thu Mar 24 13:52:29 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Mar 31 16:34:11 2006 Subject: [egenix-users] getting a gcc error durin install In-Reply-To: References: Message-ID: <4242B80D.8070608@egenix.com> Ertl, John wrote: > All, > > I am trying to install egenix-mx-commercial-2.0.7 from source and I am > getting the following error. I am not much of a systems person but Python > 2.4 and all of the modules have installed with out this problem so I am sure > what the issue might be. I am running on RedHat ES 3.0 . I could not find > this issue in the archive or on goggle. I was able to install the BASE just > fine. > > Any ideas? Looks as if you don't have the iODBC header files installed or the mxODBC is picking up a set of header files that are really ODBC header files (or from unixODBC). Please check which ODBC manager you have installed and also whether you have the development RPMs for these installed. > Thanks > > ....skipping.... > mx/ODBC/iODBC/mxODBC.c: In function `initmxODBC': > mx/ODBC/iODBC/mxODBC.c:6722: `SQLRETURN' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6722: syntax error before "rc" > mx/ODBC/iODBC/mxODBC.c:6875: `rc' undeclared (first use in this function) > mx/ODBC/iODBC/mxODBC.c:6875: warning: implicit declaration of function > `SQLAllocEnv' > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_SUCCESS' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HDBC' undeclared (first use in this > function) > mx/ODBC/iODBC/mxODBC.c:6877: `SQL_NULL_HSTMT' undeclared (first use in this > function) > error: command '/usr/bin/gcc' failed with exit status 1 > > [asd1uc8]/home/ertlj/ertljVersion/egenix-mx-commercial-2.0.7>gcc -v > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --enable-shared --enable-threads=posix > --disable-checking --with-system-zlib --enable-__cxa_atexit > --host=i386-redhat-linux > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) > > John C. Ertl > Fleet Numerical Meteorology & Oceanography Center > 7 Grace Hopper Ave > Monterey, CA 93943 > phone: (831) 656-5704 > fax: (831) 656-4363 > > > _______________________________________________________________________ > eGenix.com User Mailing List http://www.egenix.com/ > https://www.egenix.com/mailman/listinfo/egenix-users -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 24 2005) >>> 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 support at egenix.com Tue Mar 29 20:50:08 2005 From: support at egenix.com (eGenix.com Support Team: M.-A. Lemburg) Date: Fri Mar 31 16:34:11 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <000001c53478$ef063b10$6701a8c0@mem.int> References: <000001c53478$ef063b10$6701a8c0@mem.int> Message-ID: <42499550.3050807@egenix.com> Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This server is > distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from SQL's > Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database Connection > and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 remy_pinsonnault at roche.ca Tue Mar 29 14:04:33 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Mar 31 16:34:11 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> Message-ID: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Thanks Marc-Andre. I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but the SQL Server ODBC that comes with XP. I then connect the egenix Zope DA to this SQL Server ODBC. I created the SQL Server ODBC with default settings and I don't see anything like connection pooling in the configuration?! Other ideas? Thanks Remy Pinsonnault Systems Analyst Ministry of Energy and Mines, Peru -----Original Message----- From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 12:50 p.m. To: remy_pinsonnault@roche.ca Cc: egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This > server is distributed and has a connection to an Oracle 9 database. > > With the SQL Server connection, I can query the oracle tables from > SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). > > I even created an ODBC connection with the old Z ODBC Database > Connection and the query worked fine. > > But when I do the same query with mxODBC, I get the following error: > > Valor del Error > ('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The > operation could not be performed because the OLE DB provider 'MSDAORA' was > unable to begin a distributed transaction.", 5923) > > Any idea how to fix that? Please make sure that you switch off connection pooling for the used connection in the MS ODBC manager (mxODBC Zope DA has its own connection pooling - unlike the old Z ODBC product). Other than that, the following MS KB articles may be of help: * How to set up and troubleshoot a linked server to Oracle in SQL Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 * Information about using Oracle with Microsoft Transaction Server and COM+ components http://support.microsoft.com/kb/193893/EN-US/ * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider http://support.microsoft.com/kb/q244661/ Note that you may be better off with the Oracle ODBC driver, since MS does not seem to be interested in updating the MS Oracle ODBC driver anymore. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 support at egenix.com Tue Mar 29 22:21:54 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Fri Mar 31 16:34:11 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> References: <001c01c53489$c2dfd4e0$6701a8c0@mem.int> Message-ID: <4249AAD2.30800@egenix.com> Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC driver but > the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see anything > like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' was >>unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and COM+ > components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS does > not seem to be interested in updating the MS Oracle ODBC driver anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:23:04 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Mar 31 16:34:11 2006 Subject: [egenix-users] too many connections open Message-ID: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> I'm getting the following error on one or more of my connection objects: too many connection pools open, try closing a few connections If I restart Zope, I can get the connection to open, but I end up with a different connection object being closed somewhere else. Is there a hard limit to the number of Database Connections we can have at a time? ~~~ Tim Morgan, I.T. Spec. * Family & Children's Services * (918) 560-1131 * tmorgan@fcsok.org To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20050329/c9e36254/attachment-0139.htm From mal at egenix.com Tue Mar 29 22:30:20 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Mar 31 16:34:12 2006 Subject: [egenix-users] too many connections open In-Reply-To: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> References: <8dc096d5386261385781f37869bd56914249ab1c@fcsok.org> Message-ID: <4249ACCC.80506@egenix.com> Tim Morgan wrote: > I'm getting the following error on one or more of my connection objects: > > too many connection pools open, try closing a few connections > > If I restart Zope, I can get the connection to open, but I end up with a > different connection object being closed somewhere else. Is there a hard > limit to the number of Database Connections we can have at a time? There are two limits: You can have up to 20 connection pools with up to 50 connections each. Both values can be adjusted, though, if needed. Do you have more than 20 connection object open at the same time ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:31:51 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Mar 31 16:34:12 2006 Subject: [egenix-users] too many connections open Message-ID: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Yes, we have just more than 20 connection objects at this time and this number will probably be increasing shortly. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:30 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > I'm getting the following error on one or more of my > connection objects: > > > > too many connection pools open, try closing a few connections > > > > If I restart Zope, I can get the connection to open, but I > end up with > > a different connection object being closed somewhere else. > Is there a > > hard limit to the number of Database Connections we can > have at a time? > > There are two limits: You can have up to 20 connection pools > with up to 50 connections each. Both values can be adjusted, > though, if needed. > > Do you have more than 20 connection object open at the same time ? > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 ! :::: > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. From mal at egenix.com Tue Mar 29 22:50:46 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Mar 31 16:34:12 2006 Subject: [egenix-users] too many connections open In-Reply-To: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> References: <5e4a5778342d14b9f7a55d1cfb7077904249ad43@fcsok.org> Message-ID: <4249B196.6050607@egenix.com> Tim Morgan wrote: > Yes, we have just more than 20 connection objects at this time and this > number will probably be increasing shortly. I see. To adjust the limits, you will have to tweak the Zope DA globals using the following trick: Create a file ZopeDASettings.py in the same directory where you find ZopeDA.pyc (Products/mxODBCZopeDA) with the following content: """ # Schema cache #MAX_SCHEMA_CACHE_SIZE = 10 # Maximum number of Zope data sources to pool #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 # Maximum number of Zope connections to pool per data source #MAX_ZOPE_POOL_SIZE = 50 """ and uncomment and adjust the limits to your needs. You may also want to increase the schema cache size with that many connections open. A restart of Zope should then have the Zope DA pick up these new setting automatically. >>-----Original Message----- >>From: M.-A. Lemburg [mailto:mal@egenix.com] >>Sent: Tuesday, March 29, 2005 1:30 PM >>To: Tim Morgan >>Cc: egenix-users@lists.egenix.com >>Subject: Re: [egenix-users] too many connections open >> >>Tim Morgan wrote: >> >>>I'm getting the following error on one or more of my >> >>connection objects: >> >>> >>> too many connection pools open, try closing a few connections >>> >>>If I restart Zope, I can get the connection to open, but I >> >>end up with >> >>>a different connection object being closed somewhere else. >> >>Is there a >> >>>hard limit to the number of Database Connections we can >> >>have at a time? >> >>There are two limits: You can have up to 20 connection pools >>with up to 50 connections each. Both values can be adjusted, >>though, if needed. >> >>Do you have more than 20 connection object open at the same time ? >> >>-- >> >>Marc-Andre Lemburg >>eGenix.com >> >>Professional Python Services directly from the Source (#1, >>Mar 29 2005) >> >>> 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 ! :::: >> >> > > > > > To view Family & Children's Services Employment Opportunities, visit our website at http://www.fcsok.org/who_we_are/employment.asp. > > CONFIDENTIALITY NOTICE: This email, including any attachments, is intended only for the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable laws. If the reader of this message is not the intended recipient, you are hereby informed that any review, use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all forms of the original message from your system. Thank you. > > This e-mail and all other electronic (including voice) communications from the sender's agency are for informational purposes only. No such communication is intended by the sender to constitute either an electronic record or an electronic signature, or to constitute any agreement by the sender to conduct a transaction by electronic means. Any such intention or agreement is hereby expressly disclaimed unless otherwise specifically indicated. To learn more about our agency, please visit our website at http://www.fcsok.org. > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 tmorgan at fcsok.org Tue Mar 29 14:56:37 2005 From: tmorgan at fcsok.org (Tim Morgan) Date: Fri Mar 31 16:34:12 2006 Subject: [egenix-users] too many connections open Message-ID: <37bbb3289474d0b9e723b3cc2608e1cd4249b319@fcsok.org> Worked like a charm. Thanks. > -----Original Message----- > From: M.-A. Lemburg [mailto:mal@egenix.com] > Sent: Tuesday, March 29, 2005 1:51 PM > To: Tim Morgan > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-users] too many connections open > > Tim Morgan wrote: > > Yes, we have just more than 20 connection objects at this time and > > this number will probably be increasing shortly. > > I see. > > To adjust the limits, you will have to tweak the Zope DA > globals using the following trick: > > Create a file ZopeDASettings.py in the same directory where > you find ZopeDA.pyc (Products/mxODBCZopeDA) with the > following content: > > """ > # Schema cache > #MAX_SCHEMA_CACHE_SIZE = 10 > > # Maximum number of Zope data sources to pool > #MAX_ZOPE_CONNECTION_POOL_SIZE = 20 > > # Maximum number of Zope connections to pool per data source > #MAX_ZOPE_POOL_SIZE = 50 """ > > and uncomment and adjust the limits to your needs. > You may also want to increase the schema cache size with that > many connections open. > > A restart of Zope should then have the Zope DA pick up these > new setting automatically. > > >>-----Original Message----- > >>From: M.-A. Lemburg [mailto:mal@egenix.com] > >>Sent: Tuesday, March 29, 2005 1:30 PM > >>To: Tim Morgan > >>Cc: egenix-users@lists.egenix.com > >>Subject: Re: [egenix-users] too many connections open > >> > >>Tim Morgan wrote: > >> > >>>I'm getting the following error on one or more of my > >> > >>connection objects: > >> > >>> > >>> too many connection pools open, try closing a few connections > >>> > >>>If I restart Zope, I can get the connection to open, but I > >> > >>end up with > >> > >>>a different connection object being closed somewhere else. > >> > >>Is there a > >> > >>>hard limit to the number of Database Connections we can > >> > >>have at a time? > >> > >>There are two limits: You can have up to 20 connection > pools with up > >>to 50 connections each. Both values can be adjusted, though, if > >>needed. > >> > >>Do you have more than 20 connection object open at the same time ? > >> > >>-- > >> > >>Marc-Andre Lemburg > >>eGenix.com > >> > >>Professional Python Services directly from the Source (#1, Mar 29 > >>2005) > >> >>> 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 ! > >>:::: > >> > >> > > > > > > > > > > To view Family & Children's Services Employment > Opportunities, visit our website at > http://www.fcsok.org/who_we_are/employment.asp. > > > > CONFIDENTIALITY NOTICE: This email, including any > attachments, is intended only for the individual or entity to > which it is addressed and may contain information that is > privileged, confidential and exempt from disclosure under > applicable laws. If the reader of this message is not the > intended recipient, you are hereby informed that any review, > use, disclosure, distribution or copying of this > communication is strictly prohibited. If you have received > this communication in error, please contact the sender by > reply email and delete all forms of the original message from > your system. Thank you. > > > > This e-mail and all other electronic (including voice) > communications from the sender's agency are for informational > purposes only. No such communication is intended by the > sender to constitute either an electronic record or an > electronic signature, or to constitute any agreement by the > sender to conduct a transaction by electronic means. Any > such intention or agreement is hereby expressly disclaimed > unless otherwise specifically indicated. To learn more about > our agency, please visit our website at http://www.fcsok.org. > > > > -- > > Marc-Andre Lemburg > eGenix.com > > Professional Python Services directly from the Source (#1, > Mar 29 2005) > >>> 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 Mar 30 17:06:47 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Mar 31 16:34:12 2006 Subject: [egenix-users] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249A6BF.3010907@metamoof.net> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> <4249A6BF.3010907@metamoof.net> Message-ID: <424AB277.3060602@egenix.com> Moof wrote: > eGenix.com Support Team: M.-A. Lemburg wrote: > > >>Please make sure that you switch off connection pooling for >>the used connection in the MS ODBC manager (mxODBC Zope DA >>has its own connection pooling - unlike the old Z ODBC >>product). > > > Does straight mxODBC have this pooling? No, this is only implemented in the Zope DA. Would there be interest in such a feature ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 10:32:10 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Mar 31 16:34:12 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <4249AAD2.30800@egenix.com> Message-ID: <001101c53535$41d4a180$6701a8c0@mem.int> Yes I have revised the URLs you mentioned and of course MSDTS is running. With eGenix's ODBC I always get the error. In fact I can query the SQL Server's tables fine but when I do a query on the Oracle linked server tables, I always get the error. I repeat that the old ODBC Zope DA can query the Oracle linked server without a problem. I also tried connecting with the same ODBC from ASP and Powerbuilder and everything works fine. I am using the latest ODBC for SQL Server. Maybe I can send you off-list screen shots of my configuration? Thanks R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Martes, 29 de Marzo de 2005 02:22 p.m. To: remy_pinsonnault@roche.ca Cc: 'eGenix.com Support Team: M.-A. Lemburg'; egenix-users@lists.egenix.com Subject: Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) Remy Pinsonnault wrote: > Thanks Marc-Andre. > > I am not using Microsoft Oracle ODBC driver, neither Oracle ODBC > driver but the SQL Server ODBC that comes with XP. > > I then connect the egenix Zope DA to this SQL Server ODBC. > > I created the SQL Server ODBC with default settings and I don't see > anything like connection pooling in the configuration?! > > Other ideas? Have you checked the URLs I mentioned in the email ? Some other things you might want to check: * Is MSDTS running ? * Do you always get the error below or only sometimes or just for some queries ? * Does the user account you're using for Zope have proper permissions setup so that it can access MSDTS ? * Are you using the latest ODBC drivers available for SQL Server ? > Thanks > > Remy Pinsonnault > Systems Analyst > Ministry of Energy and Mines, Peru > > -----Original Message----- > From: eGenix.com Support Team: M.-A. Lemburg > [mailto:support@egenix.com] > Sent: Martes, 29 de Marzo de 2005 12:50 p.m. > To: remy_pinsonnault@roche.ca > Cc: egenix-users@lists.egenix.com > Subject: Re: [egenix-support] SQL Server connection to Oracle Bug > (Distributed Database) > > > Remy Pinsonnault wrote: > >>We are using mxODBCZopeDA-1.0.8 to connect to a SQL Server. This >>server is distributed and has a connection to an Oracle 9 database. >> >>With the SQL Server connection, I can query the oracle tables from >>SQL's Data Analyzer or from Power Builder (with a SQL Server ODBC). >> >>I even created an ODBC connection with the old Z ODBC Database >>Connection and the query worked fine. >> >>But when I do the same query with mxODBC, I get the following error: >> >>Valor del Error >>('42000', 7391, "[Microsoft][ODBC SQL Server Driver][SQL Server]The >>operation could not be performed because the OLE DB provider 'MSDAORA' >>was unable to begin a distributed transaction.", 5923) >> >>Any idea how to fix that? > > > Please make sure that you switch off connection pooling for the used > connection in the MS ODBC manager (mxODBC Zope DA has its own > connection pooling - unlike the old Z ODBC product). > > Other than that, the following MS KB articles may be of help: > > * How to set up and troubleshoot a linked server to Oracle in SQL Server > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280106 > > * Information about using Oracle with Microsoft Transaction Server and > COM+ components > http://support.microsoft.com/kb/193893/EN-US/ > > * Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider > http://support.microsoft.com/kb/q244661/ > > Note that you may be better off with the Oracle ODBC driver, since MS > does not seem to be interested in updating the MS Oracle ODBC driver > anymore. > > Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 29 2005) >>> 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 moof at metamoof.net Tue Mar 29 22:04:31 2005 From: moof at metamoof.net (Moof) Date: Fri Mar 31 16:34:12 2006 Subject: [egenix-users] Re: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <42499550.3050807@egenix.com> References: <000001c53478$ef063b10$6701a8c0@mem.int> <42499550.3050807@egenix.com> Message-ID: <4249A6BF.3010907@metamoof.net> eGenix.com Support Team: M.-A. Lemburg wrote: > Please make sure that you switch off connection pooling for > the used connection in the MS ODBC manager (mxODBC Zope DA > has its own connection pooling - unlike the old Z ODBC > product). Does straight mxODBC have this pooling? Moof -- Giles Antonio Radford - Website down, but take a peek at http://del.icio.us/moof/ "Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit..." -- Cicero, _de finibus bonorum et malorum_ From support at egenix.com Wed Mar 30 18:15:20 2005 From: support at egenix.com (eGenix Support Team: M.-A. Lemburg) Date: Fri Mar 31 16:34:12 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <001101c53535$41d4a180$6701a8c0@mem.int> References: <001101c53535$41d4a180$6701a8c0@mem.int> Message-ID: <424AC288.5000000@egenix.com> R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 remy_pinsonnault at roche.ca Wed Mar 30 11:28:05 2005 From: remy_pinsonnault at roche.ca (Remy Pinsonnault) Date: Fri Mar 31 16:34:12 2006 Subject: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) In-Reply-To: <424AC288.5000000@egenix.com> Message-ID: <001901c5353d$11c5a590$6701a8c0@mem.int> Ok thanks for your help. I will continue my investigation and I will have to buy a support ticket if I don't fint the problem. R?my -----Original Message----- From: eGenix Support Team: M.-A. Lemburg [mailto:support@egenix.com] Sent: Mi?rcoles, 30 de Marzo de 2005 10:15 a.m. To: remy_pinsonnault@roche.ca Cc: 'egenix-users@lists.egenix.com' Subject: Re: [egenix-users] RE: [egenix-support] SQL Server connection to Oracle Bug (Distributed Database) R?my, the whole subject of distributed transactions is very complex, so we can only guess at what's causing the problem without having direct access to your machine. The fact that the old ODBC DA works for you indicates that your setup has a problem with connections that are pooled to execute more than one request simultaneously. Another possible cause is that the other tools you are using are not trying to initiate a distributed transaction at all and thus don't see the problem. There's also a bug in SQL Server 2000 that may be related to the problem you are seeing: * ODBC Driver for SQL Server 2000 Incorrectly Returns SQL_SUCCESS on SQLDescribeParam() http://support.microsoft.com/default.aspx?scid=kb;en-us;321255 (mxODBC uses SQLDescribeParam() whereas the old ODBC DA does not) Some more problem cases are described in the MS knowledge base: http://support.microsoft.com/search/default.aspx?query=7391+OLE+DB&catalog=L CID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode= a&x=0&y=0 This one sounds like a good candidate to check: * You may receive a 7391 error message in SQL Server 2000 when you run a distributed transaction against a linked server after you install Microsoft Windows XP Service Pack 2 http://support.microsoft.com/default.aspx?scid=kb;en-us;839279 When debugging problems like these, please always start Zope from a command window - not as service. If that works, try finding out which permissions are needed to access the various components involved in the distributed transaction and update the policy of the Zope service account accordingly. Please note that our support is not free of charge. If you want us to help you beyond the links and hints we've already given you so far, please purchase a support ticket from our web-site. We can also provide remote login support if needed to help you resolve the problem. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 30 2005) >>> 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 ! ::::